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.

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

Closed
russellb opened this issue Jul 30, 2019 · 3 comments · Fixed by #789
Closed

Drop custom image registry config manifest #704

russellb opened this issue Jul 30, 2019 · 3 comments · Fixed by #789
Assignees

Comments

@russellb
Copy link
Member

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

@dhellmann
Copy link
Member

@russellb I see #623 refers to this. Does that resolve this issue, or is there still work to do?

@russellb
Copy link
Member Author

There's still work to do. 99_registry.yaml is still there. It's pending outcome of openshift/cluster-image-registry-operator#332

@russellb
Copy link
Member Author

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants