// Module included in the following assemblies:
//
// * installing/installing_bare_metal/installing-bare-metal.adoc
// * installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc
// * installing/installing_vsphere/installing-restricted-networks-vsphere.adoc
// * installing/installing_vsphere/installing-vsphere.adoc
// * registry/configuring-registry-storage/configuring-registry-storage-baremetal.adoc
// * registry/configuring-registry-storage/configuring-registry-storage-vsphere.adoc

[id="registry-change-management-state_{context}"]
= Change image registry ManagementState

To start the image registry, you must change `ManagementState` Image Registry Operator configuration from `Removed` to `Managed`.

.Procedure

* Change `ManagementState` Image Registry Operator configuration from `Removed` to `Managed`. For example:
+
[source,yaml]
----
apiVersion: imageregistry.operator.openshift.io/v1
kind: Config
metadata:
  creationTimestamp: <time>
  finalizers:
    - imageregistry.operator.openshift.io/finalizer
  generation: 3
  name: cluster
  resourceVersion:  <version>
  selfLink: <link>
spec:
  readOnly: false
  disableRedirect: false
  requests:
    read:
      maxInQueue: 0
      maxRunning: 0
      maxWaitInQueue: 0s
    write:
      maxInQueue: 0
      maxRunning: 0
      maxWaitInQueue: 0s
  defaultRoute: true
  managementState: Managed
----

// Module included in the following assemblies:
//
// * installing/installing_bare_metal/installing-bare-metal.adoc
// * installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc
// * installing/installing_vsphere/installing-restricted-networks-vsphere.adoc
// * installing/installing_vsphere/installing-vsphere.adoc
// * registry/configuring_registry_storage/configuring-registry-storage-baremetal.adoc
// * registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc
// * virt/virtual_machines/importing_vms/virt-importing-vmware-vm.adoc

[id="registry-change-management-state_{context}"]
= Changing the image registry's management state

To start the image registry, you must change the Image Registry Operator configuration's `managementState` from `Removed` to `Managed`.

.Procedure

* Change `managementState` Image Registry Operator configuration from `Removed` to `Managed`. For example:
+
[source,terminal]
----
$ oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{"spec":{"managementState":"Managed"}}'
----

Simplify command to change managementState
Simplify command to change managementState

The working example shows the image registry operator config object, but the command to change the ManagementState by editing it is not provided.  As a reference, this would suffice: `oc edit configs.imageregistry.operator.openshift.io`.  However, a simpler instruction for the user would be to patch in place, command provided by this proposed commit.
