This repository has been archived by the owner on Mar 23, 2020. It is now read-only.
Provide production configuration for the image registry operator #5
Comments
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
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So far in dev-scripts, we have been manually configuring the image registry operator to use the
emptyDirbackend. This just makes it use local storage, and is not intended for any production use.https://github.com/openshift-metal3/dev-scripts/blob/master/assets/templates/99_registry.yaml
In the following PR, I've proposed a patch to move this default into the image registry operator, so we can drop this manifest from dev-scripts and still have the cluster deploy cleanly.
openshift/cluster-image-registry-operator#332
Since emptyDir is not a production backend for the registry,
install-scriptsneeds to immediately reconfigure it to use a PVC after OCS has been deployed and a PVC can be created.The text was updated successfully, but these errors were encountered: