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
Drop custom image registry config manifest #704
Comments
There's still work to do. 99_registry.yaml is still there. It's pending outcome of openshift/cluster-image-registry-operator#332 |
openshift/cluster-image-registry-operator#332 has merged so we can remove the registry manifest once that shows up in a nightly release |
russellb
added a commit
to russellb/dev-scripts
that referenced
this issue
Sep 3, 2019
The cluster-image-registry-operator will now use emptyDir by default for the "baremetal" infrastructure platform, so this manifest is no longer needed. openshift/cluster-image-registry-operator#332 Note this is still not a supported configuration, and is only used to bring up the cluster. It should be immediately reconfigured to use a PVC once storage has been set up. For more info on that post-install task, see: openshift-kni/install-scripts#5 Closes openshift-metal3#704
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is to track the removal of:
https://github.com/openshift-metal3/dev-scripts/blob/master/assets/templates/99_registry.yaml
It can be removed when the following PR is merged:
openshift/cluster-image-registry-operator#332
The text was updated successfully, but these errors were encountered: