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

Support basic operator upgrades #65

Closed
phoracek opened this issue Apr 13, 2019 · 3 comments
Closed

Support basic operator upgrades #65

phoracek opened this issue Apr 13, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@phoracek
Copy link
Member

phoracek commented Apr 13, 2019 •
edited
Loading

We should be able to upgrade operator and deployed components to a newer version. In the first implementation all we should support is upgrading image name and adding new objects to Kubernetes API. Removals of old objects won't be supported in the initial implementation.

We may need to resolve #34 to fully support upgrades.
@phoracek phoracek self-assigned this Apr 13, 2019
@phoracek phoracek added this to the 0.4.0 milestone Apr 13, 2019
@phoracek phoracek changed the title Support operator upgrades Support basic operator upgrades Apr 13, 2019
@phoracek phoracek mentioned this issue Apr 13, 2019
Closed
@phoracek phoracek modified the milestones: 0.5.0, 0.4.0 Apr 16, 2019
@phoracek
Copy link
Member Author

phoracek commented Jun 2, 2019

I tested the upgrade manually and it works (I reapplied operator manifest, where all images were set to :latest and it eventually upgraded all components). However, it is not possible to monitor the upgrade and current version through State fields. We should add a functional test for the upgrade and extend reporting functionality.

@phoracek phoracek removed their assignment Jun 2, 2019
@phoracek phoracek added the enhancement New feature or request label Jun 2, 2019
@kubevirt-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@phoracek
Copy link
Member Author

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@phoracek @kubevirt-bot