<commit_before>// Module included in the following assemblies:
//
// * machine_management/creating-infrastructure-machinesets.adoc

[id="infrastructure-moving-registry_{context}"]
= Moving the default registry

You configure the registry Operator to deploy its pods to different nodes.

.Prerequisites

* Configure additional MachineSets in your {product-title} cluster.

.Procedure

. View the `config/instance` object:
+
----
$ oc get config/cluster -n openshift-ingress -o yaml
----
+
The output resembles the following text:
+
[source,yaml]
----
apiVersion: imageregistry.operator.openshift.io/v1
kind: Config
metadata:
  creationTimestamp: 2019-02-05T13:52:05Z
  finalizers:
  - imageregistry.operator.openshift.io/finalizer
  generation: 1
  name: cluster
  resourceVersion: "56174"
  selfLink: /apis/imageregistry.operator.openshift.io/v1/configs/cluster
  uid: 36fd3724-294d-11e9-a524-12ffeee2931b
spec:
  httpSecret: d9a012ccd117b1e6616ceccb2c3bb66a5fed1b5e481623
  logging: 2
  managementState: Managed
  proxy: {}
  replicas: 1
  requests:
    read: {}
    write: {}
  storage:
    s3:
      bucket: image-registry-us-east-1-c92e88cad85b48ec8b312344dff03c82-392c
      region: us-east-1
status:
...
----

. Edit the `config/instance` object:
+
----
$ oc edit config/cluster -n openshift-ingress
----

. Add the following lines of text the `spec` section of the object:
+
[source,yaml]
----
  nodeSelector:
    node-role.kubernetes.io/infra: ""
----
+
After you save and exit you can see the registry pod being moving to the
infrastructure node.<commit_msg>Remove "-n openshift-ingress"<commit_after>// Module included in the following assemblies:
//
// * machine_management/creating-infrastructure-machinesets.adoc

[id="infrastructure-moving-registry_{context}"]
= Moving the default registry

You configure the registry Operator to deploy its pods to different nodes.

.Prerequisites

* Configure additional MachineSets in your {product-title} cluster.

.Procedure

. View the `config/instance` object:
+
----
$ oc get config/cluster -o yaml
----
+
The output resembles the following text:
+
[source,yaml]
----
apiVersion: imageregistry.operator.openshift.io/v1
kind: Config
metadata:
  creationTimestamp: 2019-02-05T13:52:05Z
  finalizers:
  - imageregistry.operator.openshift.io/finalizer
  generation: 1
  name: cluster
  resourceVersion: "56174"
  selfLink: /apis/imageregistry.operator.openshift.io/v1/configs/cluster
  uid: 36fd3724-294d-11e9-a524-12ffeee2931b
spec:
  httpSecret: d9a012ccd117b1e6616ceccb2c3bb66a5fed1b5e481623
  logging: 2
  managementState: Managed
  proxy: {}
  replicas: 1
  requests:
    read: {}
    write: {}
  storage:
    s3:
      bucket: image-registry-us-east-1-c92e88cad85b48ec8b312344dff03c82-392c
      region: us-east-1
status:
...
----

. Edit the `config/instance` object:
+
----
$ oc edit config/cluster
----

. Add the following lines of text the `spec` section of the object:
+
[source,yaml]
----
  nodeSelector:
    node-role.kubernetes.io/infra: ""
----
+
After you save and exit you can see the registry pod being moving to the
infrastructure node.
{'fraction_non_alphanumeric': 0.11454311454311454, 'fraction_numerical': 0.06113256113256113, 'mean_word_length': 3.7465648854961833, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2356426', 'n_tokens_mistral': 1185, 'n_tokens_neox': 1039, 'n_words': 261}