Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Behavior of spec.version when not specified: Discussion #164

Closed
tmshort opened this issue Apr 11, 2023 · 0 comments
Closed

Behavior of spec.version when not specified: Discussion #164

tmshort opened this issue Apr 11, 2023 · 0 comments

Comments

@tmshort
Copy link
Contributor

tmshort commented Apr 11, 2023

What is the behavior of spec.version when not specified? There are multiple possibilities, some of which are listed here:

  1. Not valid; spec.version must be specified.
  2. spec.version is optional, when not specified, nothing happens.
  3. A non-specified spec.version means "latest", such that it can be used to upgrade to the latest version of an operator when it becomes available.
  4. A non-specified spec.version means "any", such that when initially created, it will refer to any available version (for example, "latest"). On subsequent updates, a non-specified spec.version will match the currently installed version, so no updates occur.
@tmshort tmshort changed the title Behavior of spec.version when not specified Behavior of spec.version when not specified: Discussion Apr 11, 2023
@operator-framework operator-framework locked and limited conversation to collaborators Apr 11, 2023
@joelanford joelanford converted this issue into discussion #165 Apr 11, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant