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
Simplify Image Handling #3430
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Right now there are two main causes of confusion and complexity around container images in the repo:
a. annotating the
HostedCluster
b. providing flags to the
hypershift-operator
c. setting spec fields in the
HostedCluster
d. self-referential live lookups using the in-cluster client
availability-prober
,control-plane-operator
, etc) when there is in fact just oneIdeally, we should determine if a) any production environment needs to support multiple component images and, if not, remove that concept as well as b) simplify the many avenues for determining what images are used, and when.
The text was updated successfully, but these errors were encountered: