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

Question: auto update enabled #99

Open
jatanmalde opened this issue Jan 23, 2019 · 4 comments
Open

Question: auto update enabled #99

jatanmalde opened this issue Jan 23, 2019 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@jatanmalde
Copy link

Question: How does the CVO monitors for new image when auto-update is enabled?

How does it looks for new ocp-release image when pushed to the container catalog(which would be used in future for ocp 4.0 if I am not wrong)?

Let me know your thoughts on it.
@jatanmalde
Copy link
Author

Hello,

Any updates on this?

@wking
Copy link
Member

wking commented May 29, 2019

How does it looks for new ocp-release image...

ClusterVersion's Upstream and Channel properties tell it where to find Cincinnati. There's currently no knob for making those automatic outside of the --enable-auto-update option, though. We'll probably need to expand the API to give a ClusterVersion spec knob for that.

@wking wking mentioned this issue May 29, 2019
Closed
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 10, 2020
@wking
Copy link
Member

wking commented Sep 10, 2020

/lifecycle frozen

Still waiting on buy-in in openshift/enhancements#124.

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wking @openshift-bot @jatanmalde @openshift-ci-robot