Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Upgrade Support #142

Closed
danehans opened this issue Dec 2, 2020 · 3 comments · Fixed by #316
Closed

Upgrade Support #142

danehans opened this issue Dec 2, 2020 · 3 comments · Fixed by #316
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@danehans
Copy link
Contributor

danehans commented Dec 2, 2020

Please describe the problem you have
How do users upgrade from one release of Contour to another? Is this as simple as upgrading the operator? Will the upgrade be zero downtime?

/cc @Miciah
@danehans danehans added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 2, 2020
@danehans danehans mentioned this issue Dec 2, 2020
Open
@youngnick
Copy link
Member

Seems like right now the answers are:

  • You upgrade the operator, that upgrades Contour
  • This is not zero downtime, depending on the exact details of the upgrade.

@danehans danehans mentioned this issue Feb 17, 2021
Open
@danehans
Copy link
Contributor Author

Ensure Contour|GatewayClass|Gateway resources are reporting expected status conditions during the upgrade process.

This was referenced Apr 14, 2021
Closed
Closed
@danehans
Copy link
Contributor Author

Will the upgrade be zero downtime?

As a first step in supporting upgrades, I suggest not requiring zero downtime. This issue should provide repeatable, tested upgrades from the previous release to the latest release.

@danehans danehans mentioned this issue Apr 19, 2021
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adds e2e Upgrade Test danehans/contour-operator
2 participants
@danehans @youngnick