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

Support advanced operator upgrade #67

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

Support advanced operator upgrade #67

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

Comments

@phoracek
Copy link
Member

phoracek commented Apr 13, 2019

Improve operator upgrades. One of the missing features (in #65) that comes to my mind is possibility to remove objects that are not needed anymore. e.g. when previous version deployed a configmap as a part of component X, but in the new version the configmap is not part of X manifests anymore.

@phoracek phoracek closed this as completed Jun 2, 2019
@phoracek phoracek reopened this 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

phoracek commented Sep 1, 2019

Still needed. We already have a workaround in our code (removal of old bridge-marker). That would be resolved with this enhancement.

/remove-lifecycle stale

@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

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 30, 2019
@kubevirt-bot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 30, 2019
@phoracek
Copy link
Member Author

phoracek commented Jan 2, 2020

/remove-lifecycle stale
/close

Resolved via #270

@kubevirt-bot
Copy link
Collaborator

@phoracek: Closing this issue.

In response to this:

/remove-lifecycle stale
/close

Resolved via #270

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@phoracek
Copy link
Member Author

phoracek commented Jan 2, 2020

/remove-lifecycle rotten

@kubevirt-bot kubevirt-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants