|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * installing/installing_with_agent_based_installer/installing-with-agent-basic.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: PROCEDURE |
| 6 | +[id="installing-ocp-agent-basic-inputs_{context}"] |
| 7 | += Creating the configuration inputs |
| 8 | + |
| 9 | + |
| 10 | +You must create the configuration files that are used by the installation program to create the agent image. |
| 11 | + |
| 12 | +.Procedure |
| 13 | + |
| 14 | +. Place the `openshift-install` binary in a directory that is on your PATH. |
| 15 | + |
| 16 | +. Create a directory to store the install configuration by running the following command: |
| 17 | ++ |
| 18 | +[source,terminal] |
| 19 | +---- |
| 20 | +$ mkdir ~/<directory_name> |
| 21 | +---- |
| 22 | + |
| 23 | +. Create the `install-config.yaml` file by running the following command: |
| 24 | ++ |
| 25 | +-- |
| 26 | +[source,terminal] |
| 27 | +---- |
| 28 | +$ cat << EOF > ./my-cluster/install-config.yaml |
| 29 | +apiVersion: v1 |
| 30 | +baseDomain: test.example.com |
| 31 | +compute: |
| 32 | +- architecture: amd64 // <1> |
| 33 | + hyperthreading: Enabled |
| 34 | + name: worker |
| 35 | + replicas: 0 |
| 36 | +controlPlane: |
| 37 | + architecture: amd64 |
| 38 | + hyperthreading: Enabled |
| 39 | + name: master |
| 40 | + replicas: 1 |
| 41 | +metadata: |
| 42 | + name: sno-cluster // <2> |
| 43 | +networking: |
| 44 | + clusterNetwork: |
| 45 | + - cidr: fd01::/48 |
| 46 | + hostPrefix: 64 |
| 47 | + machineNetwork: |
| 48 | + - cidr: fd2e:6f44:5dd8:c956::/120 |
| 49 | + networkType: OVNKubernetes // <3> |
| 50 | + serviceNetwork: |
| 51 | + - fd02::/112 |
| 52 | +platform: <4> |
| 53 | + none: {} |
| 54 | +pullSecret: '<pull_secret>' // <5> |
| 55 | +sshKey: '<ssh_pub_key>' // <6> |
| 56 | +additionalTrustBundle: | // <7> |
| 57 | + -----BEGIN CERTIFICATE----- |
| 58 | + ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ |
| 59 | + -----END CERTIFICATE----- |
| 60 | +imageContentSources: // <8> |
| 61 | +- mirrors: |
| 62 | + - <local_registry>/<local_repository_name>/release |
| 63 | + source: quay.io/openshift-release-dev/ocp-release |
| 64 | +- mirrors: |
| 65 | + - <local_registry>/<local_repository_name>/release |
| 66 | + source: quay.io/openshift-release-dev/ocp-v4.0-art-dev |
| 67 | +EOF |
| 68 | +---- |
| 69 | +<1> Specify the system architecture. Valid values are `amd64`, `arm64`, `ppc64le`, and `s390x`. |
| 70 | ++ |
| 71 | +If you are using the release image with the `multi` payload, you can install the cluster on different architectures such as `arm64`, `amd64`, `s390x`, and `ppc64le`. Otherwise, you can install the cluster only on the `release architecture` displayed in the output of the `openshift-install version` command. For more information, see "Verifying the supported architecture for installing an Agent-based Installer cluster". |
| 72 | +<2> Required. Specify your cluster name. |
| 73 | +<3> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value. |
| 74 | +<4> Specify your platform. |
| 75 | ++ |
| 76 | +[NOTE] |
| 77 | +==== |
| 78 | +For bare metal platforms, host settings made in the platform section of the `install-config.yaml` file are used by default, unless they are overridden by configurations made in the `agent-config.yaml` file. |
| 79 | +==== |
| 80 | +<5> Specify your pull secret. |
| 81 | +<6> Specify your SSH public key. |
| 82 | +<7> Provide the contents of the certificate file that you used for your mirror registry. |
| 83 | +The certificate file can be an existing, trusted certificate authority or the self-signed certificate that you generated for the mirror registry. |
| 84 | +You must specify this parameter if you are using a disconnected mirror registry. |
| 85 | +<8> Provide the `imageContentSources` section according to the output of the command that you used to mirror the repository. |
| 86 | +You must specify this parameter if you are using a disconnected mirror registry. |
| 87 | ++ |
| 88 | +[IMPORTANT] |
| 89 | +==== |
| 90 | +* When using the `oc adm release mirror` command, use the output from the `imageContentSources` section. |
| 91 | +* When using the `oc mirror` command, use the `repositoryDigestMirrors` section of the `ImageContentSourcePolicy` file that results from running the command. |
| 92 | +* The `ImageContentSourcePolicy` resource is deprecated. |
| 93 | +==== |
| 94 | +-- |
| 95 | +
|
| 96 | +. Create the `agent-config.yaml` file by running the following command: |
| 97 | ++ |
| 98 | +[source,terminal] |
| 99 | +---- |
| 100 | +$ cat > agent-config.yaml << EOF |
| 101 | +apiVersion: v1beta1 |
| 102 | +kind: AgentConfig |
| 103 | +metadata: |
| 104 | + name: sno-cluster |
| 105 | +rendezvousIP: fd2e:6f44:5dd8:c956::50 // <1> |
| 106 | +EOF |
| 107 | +---- |
| 108 | ++ |
| 109 | +<1> This IP address is used to determine which node performs the bootstrapping process as well as running the `assisted-service` component. |
| 110 | +You must provide the rendezvous IP address when you do not specify at least one host IP address in the `networkConfig` parameter. If this address is not provided, one IP address is selected from the provided host `networkConfig` parameter. |
0 commit comments