Skip to content

How to upgrade the operator smoothly without deleting and rebuilding? #2750

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

Open
AllenZMC opened this issue Apr 20, 2022 · 5 comments
Open
Assignees
Milestone

Comments

@AllenZMC
Copy link

Question

How to upgrade the operator smoothly without deleting and rebuilding?

Environment

  • operator-lifecycle-manager version:
    0.16.2
@needleshaped
Copy link

needleshaped commented Apr 20, 2022

Duplicate of #2664/#2694/#2695

@AllenZMC
Copy link
Author

AllenZMC commented Apr 20, 2022

When I upgrade opertaor, assuming that the new csv version is 0.0.2, and its replace field value is 0.0.1, will olm delete the csv version 0.0.1 at this time?

@exdx
Copy link
Member

exdx commented Apr 28, 2022

Hi @AllenZMC

The v0.0.1 CSV is not deleted until the new CSV v0.0.2 is in the succeeded state. There should be a doc that has some additional information on the CSV update process, we should be able to provide that here.

@exdx exdx added this to the 0.22.0 milestone Apr 28, 2022
@exdx exdx self-assigned this Apr 28, 2022
@AllenZMC
Copy link
Author

AllenZMC commented Apr 29, 2022

The v0.0.1 CSV is not deleted until the new CSV v0.0.2 is in the succeeded state.

@exdx Thanks. So similar to the grayscale release, the traffic will not be interrupted?

@AllenZMC
Copy link
Author

AllenZMC commented Apr 29, 2022

There should be a doc that has some additional information on the CSV update process, we should be able to provide that here.

Looking forward to seeing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants