-
Notifications
You must be signed in to change notification settings - Fork 461
templates: drop files related to registry #225
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
templates: drop files related to registry #225
Conversation
`cluster-image-registry-operator` now owns setting these up for access to internal registry. https://github.com/openshift/cluster-image-registry-operator/blob/master/deploy/08-ca-daemonset.yaml#L26-L46 This fixes MCD and the `cluster-image-registry-operator` stepping on each other. And MCD currently reboot on syncing any change which causes disruption on masters recurringly.
|
/lgtm Offloading registry certs to the registry operator and |
|
Hrm, router didn't come up: Maybe there's a chicken/egg with one of these files? |
|
/retest Just in case we get lucky... |
|
/retest |
|
So one potential issue with being able to unilaterally merge this would be that, as described in openshift/cluster-dns-operator#63, the DNS operator is currently just appending to |
|
/retest |
|
/lgtm |
ab8d603 to
96b62bb
Compare
|
openshift/cluster-storage-operator#5 Need this ^^ |
|
/override ci/prow/e2e-aws |
|
Fat-fingered it. Should we remove the debug commit? |
1bacac3 to
280f078
Compare
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, crawford, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
|
/retest |
|
Why is that oc error being printed? |
280f078 to
f22ae39
Compare
|
New changes are detected. LGTM label has been removed. |
|
force pushed as previously i have seen the release image being reused in same namespace. so that i can get the changes from openshift/cluster-storage-operator#5 |
|
Link? |
|
Ah, you aren’t getting a new release image when other tags change (outside of this project). Might be time to change that. |
Yeah, in one of my PRs in this repo i vaguely remember something like that happening.. i don't remember which 😇 |
enable sample imagestreams and templates on Z
cluster-image-registry-operatornow owns setting these up for access to internal registry.https://github.com/openshift/cluster-image-registry-operator/blob/master/deploy/08-ca-daemonset.yaml#L26-L46
This fixes MCD and the
cluster-image-registry-operatorstepping on each other. And MCD currently reboot on syncing anychange which causes disruption on masters recurringly.
Should help dropping ownership of
/etc/hostsand/etc/docker.d/certs/...from daemon#224 (comment)