CODEWITHSUNDEEP
kubernetesopenshiftkubernetes-podreplicasetkubernetes-deployment
DizzyThermal
DizzyThermal

Reputation: 114

How do I modify the OpenShift image-registry Deployment?

When I edit the image-registry Deployment (in the openshift-image-registry Namespace/Project), the modified fields are automatically reverted/rolled-back on Save.

My understanding is that Deployments control/manage some resources (i.e., ReplicaSets), but what Resource/CustomResource/CustomResourceDefinition controls/manages Deployments?

I'm unsure how to set a different securityContext > fsGroup for my image-registry pod because the Deployment changes I make are being reverted/rolled-back.

Upvotes: 0

Views: 1281

Answers (1)

Dennis
Dennis

Reputation: 57

That resource is managed by the image-registry operator. You can check for yourself with oc get clusteroperator image-registry and edit the configuration for the operator with oc edit configs.imageregistry.operator.openshift.io.

It is possible to set the image-registry operator in Unmanaged state, by editing configs.imageregistry.operator.openshift.io and setting managementState to Unmanaged. This would prevent the operator from actively managing its components and should allow you to change the ReplicaSet without the operator reverting your changes. Please note that setting the operator in Unmanaged state is not supported by Red Hat.

You can find more in depth documentation on the registry in the registry chapter of the OpenShift documentation.

Upvotes: 1

Related Questions