openshift / openshift/cluster-version-operator
Question: auto update enabled
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 92
- Forks
- 250
- Avg merge
- 8d 21h
- Merged PRs (30d)
- 4
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin by tracing how CVO handles auto-update checks and ocp-release images, then document the verified image-discovery behavior; the issue does not define a concrete change or completion test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100