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.

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

[epic] Support upgrades of OLMv1 itself #982

Open
joelanford opened this issue Jun 26, 2024 · 0 comments
Open

[epic] Support upgrades of OLMv1 itself #982

joelanford opened this issue Jun 26, 2024 · 0 comments
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0

Comments

@joelanford
Copy link
Member

joelanford commented Jun 26, 2024

In order to make OLMv1 more than just a toy project upstream, we need to put effort into making it actually upgradeable in upstream Kubernetes clusters.

At a minimum, this would entail:

  1. Documentation that lists valid upgrade paths
  2. Testing, that provides confidence for making changes that will not break upgrades (and perhaps that could even report valid upgrade edges automatically)
  3. A release process that makes new releases available in a consumable and consistent way.

If I'm dreaming big, I think this could look like:

@joelanford joelanford added epic v1.x Issues related to OLMv1 features that come after 1.0 labels Jun 26, 2024
@joelanford joelanford mentioned this issue Jul 5, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0
Projects
Status: No status
Development

No branches or pull requests

1 participant