Skip to content

Clarify the behaviour of multiple Operator versions installed in the same cluster #32152

@vmuzikar

Description

@vmuzikar

Description

  • Document that all Operator versions use a single CRD API version. The CRD revisions between Operator versions don't introduce any breaking changes so they are backward compatible.
  • OLM seems to keep the latest CRD revision regardless of in which order the Operator versions were installed. (This needs double checking.) Make sure to document this. Add a note for non-OLM installs that they should mimic this behaviour (installing latest CRD revision).
  • Document that using a field introduced in a newer Operator version with and older Operator version is not supported and will lead to Operator failing on an unrecognized field.

Discussion

No response

Motivation

No response

Details

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions