Skip to content
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.

Sign up for GitHub

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

Jump to bottom

📖 F28 - Provided service versions (aka 'Operand versioning') #180

Merged
merged 4 commits into from
Feb 19, 2024
Merged

📖 F28 - Provided service versions (aka 'Operand versioning') #180

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
eea388b
F28 - Provided service versions (aka 'Operand versioning')
Apr 20, 2023
c05a40f
Merge branch 'main' of https://github.com/tlwu2013/operator-controlle…
Jun 7, 2023
97c2577
sync upstream
Jul 31, 2023
bb501bf
F28 - Provided service versions (aka 'Operand versioning')
Apr 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/olmv1_roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,10 @@ OLM should have an opinion about how administrators can carry out roll outs of n
### F27 - Pluggable certificate management (P2)
OLM should rely on other controllers to create and lifecycle TLS certificates required to drive the functionality of certain extensions, like webhooks that need to trust / need to be trusted by the cluster's API server. OLM should not implement any certificate handling itself. In a first implementation support should be established for cert-manager.

### F28 - Provided service versions (P2)
Workload-based extensions can offer multiple services (a.k.a. operands) and their respective versions. Extension admins need to see which operand versions each extension supports by the extension version. Extension admins are guaranteed to install or upgrade an extension that supports their desired operand version(s). Extension authors can list supported operand versions and have guarantees that they can list dependencies that support the necessary operand version(s). When mirroring a catalog, mirroring users can select a subset of the related images to mirror, based on desired operand version(s).


# Behavioral Requirements

_Priority Rating: 1 highest, 2 medium, 3 lower (ex. P2 = Medium Priority)_
Expand Down
Loading