Manually installing a single-node OpenShift cluster with ZTP

You can deploy a managed single-node OpenShift cluster by using Red Hat Advanced Cluster Management (RHACM) and the assisted service.

If you are creating multiple managed clusters, use the SiteConfig method described in Deploying far edge sites with ZTP.

The target bare-metal host must meet the networking, firmware, and hardware requirements listed in Recommended cluster configuration for vDU application workloads.

Generating GitOps ZTP installation and configuration CRs manually

Use the generator entrypoint for the ztp-site-generate container to generate the site installation and configuration custom resource (CRs) for a cluster based on SiteConfig and PolicyGenTemplate CRs.

Prerequisites

  • You have installed the OpenShift CLI (oc).

  • You have logged in to the hub cluster as a user with cluster-admin privileges.

Procedure

  1. Create an output folder by running the following command:

    1. $ mkdir -p ./out

  2. Export the argocd directory from the ztp-site-generate container image:

    1. $ podman run --log-driver=none --rm registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4 extract /home/ztp --tar | tar x -C ./out

    The ./out directory has the reference PolicyGenTemplate and SiteConfig CRs in the out/argocd/example/ folder.

    Example output

    1. out
    2.  └── argocd
    3.       └── example
    4.            ├── policygentemplates
    5.            │     ├── common-ranGen.yaml
    6.            │     ├── example-sno-site.yaml
    7.            │     ├── group-du-sno-ranGen.yaml
    8.            │     ├── group-du-sno-validator-ranGen.yaml
    9.            │     ├── kustomization.yaml
    10.            │     └── ns.yaml
    11.            └── siteconfig
    12.                   ├── example-sno.yaml
    13.                   ├── KlusterletAddonConfigOverride.yaml
    14.                   └── kustomization.yaml

  3. Create an output folder for the site installation CRs:

    1. $ mkdir -p ./site-install

  4. Modify the example SiteConfig CR for the cluster type that you want to install. Copy example-sno.yaml to site-1-sno.yaml and modify the CR to match the details of the site and bare-metal host that you want to install, for example:

    1. # example-node1-bmh-secret & assisted-deployment-pull-secret need to be created under same namespace example-sno
    2. ---
    3. apiVersion: ran.openshift.io/v1
    4. kind: SiteConfig
    5. metadata:
    6.   name: "example-sno"
    7.   namespace: "example-sno"
    8. spec:
    9.   baseDomain: "example.com"
    10.   pullSecretRef:
    11.     name: "assisted-deployment-pull-secret"
    12.   clusterImageSetNameRef: "openshift-4.10"
    13.   sshPublicKey: "ssh-rsa AAAA..."
    14.   clusters:
    15.     - clusterName: "example-sno"
    16.       networkType: "OVNKubernetes"
    17.       # installConfigOverrides is a generic way of passing install-config
    18.       # parameters through the siteConfig.  The 'capabilities' field configures
    19.       # the composable openshift feature.  In this 'capabilities' setting, we
    20.       # remove all but the marketplace component from the optional set of
    21.       # components.
    22.       # Notes:
    23.       # - NodeTuning is needed for 4.13 and later, not for 4.12 and earlier
    24.       installConfigOverrides: '{"capabilities":{"baselineCapabilitySet": "None", "additionalEnabledCapabilities": [ "marketplace", "NodeTuning" ] }}'
    25.       # It is strongly recommended to include crun manifests as part of the additional install-time manifests for 4.13+.
    26.       # The crun manifests can be obtained from source-crs/optional-extra-manifest/ and added to the git repo ie.sno-extra-manifest.
    27.       # extraManifestPath: sno-extra-manifest
    28.       clusterLabels:
    29.         # These example cluster labels correspond to the bindingRules in the PolicyGenTemplate examples
    30.         du-profile: "4.14"
    31.         # These example cluster labels correspond to the bindingRules in the PolicyGenTemplate examples in ../policygentemplates:
    32.         # ../policygentemplates/common-ranGen.yaml will apply to all clusters with 'common: true'
    33.         common: true
    34.         # ../policygentemplates/group-du-sno-ranGen.yaml will apply to all clusters with 'group-du-sno: ""'
    35.         group-du-sno: ""
    36.         # ../policygentemplates/example-sno-site.yaml will apply to all clusters with 'sites: "example-sno"'
    37.         # Normally this should match or contain the cluster name so it only applies to a single cluster
    38.         sites: "example-sno"
    39.       clusterNetwork:
    40.         - cidr: 1001:1::/48
    41.           hostPrefix: 64
    42.       machineNetwork:
    43.         - cidr: 1111:2222:3333:4444::/64
    44.       serviceNetwork:
    45.         - 1001:2::/112
    46.       additionalNTPSources:
    47.         - 1111:2222:3333:4444::2
    48.       # Initiates the cluster for workload partitioning. Setting specific reserved/isolated CPUSets is done via PolicyTemplate
    49.       # please see Workload Partitioning Feature for a complete guide.
    50.       cpuPartitioningMode: AllNodes
    51.       # Optionally; This can be used to override the KlusterletAddonConfig that is created for this cluster:
    52.       #crTemplates:
    53.       #  KlusterletAddonConfig: "KlusterletAddonConfigOverride.yaml"
    54.       nodes:
    55.         - hostName: "example-node1.example.com"
    56.           role: "master"
    57.           # Optionally; This can be used to configure desired BIOS setting on a host:
    58.           #biosConfigRef:
    59.           #  filePath: "example-hw.profile"
    60.           bmcAddress: "idrac-virtualmedia+https://[1111:2222:3333:4444::bbbb:1]/redfish/v1/Systems/System.Embedded.1"
    61.           bmcCredentialsName:
    62.             name: "example-node1-bmh-secret"
    63.           bootMACAddress: "AA:BB:CC:DD:EE:11"
    64.           # Use UEFISecureBoot to enable secure boot
    65.           bootMode: "UEFI"
    66.           rootDeviceHints:
    67.             wwn: "0x11111000000asd123"
    68.             # example of diskPartition below is used for image registry (check ImageRegistry.md for more details), but it's not limited to this use case
    69.           #        diskPartition:
    70.           #          - device: /dev/disk/by-id/wwn-0x11111000000asd123 # match rootDeviceHints
    71.           #            partitions:
    72.           #              - mount_point: /var/imageregistry
    73.           #                size: 102500
    74.           #                start: 344844
    76.           nodeNetwork:
    77.             interfaces:
    78.               - name: eno1
    79.                 macAddress: "AA:BB:CC:DD:EE:11"
    80.             config:
    81.               interfaces:
    82.                 - name: eno1
    83.                   type: ethernet
    84.                   state: up
    85.                   ipv4:
    86.                     enabled: false
    87.                   ipv6:
    88.                     enabled: true
    89.                     address:
    90.                       # For SNO sites with static IP addresses, the node-specific,
    91.                       # API and Ingress IPs should all be the same and configured on
    92.                       # the interface
    93.                       - ip: 1111:2222:3333:4444::aaaa:1
    94.                         prefix-length: 64
    95.               dns-resolver:
    96.                 config:
    97.                   search:
    98.                     - example.com
    99.                   server:
    100.                     - 1111:2222:3333:4444::2
    101.               routes:
    102.                 config:
    103.                   - destination: ::/0
    104.                     next-hop-interface: eno1
    105.                     next-hop-address: 1111:2222:3333:4444::1
    106.                     table-id: 254

    Once you have extracted reference CR configuration files from the out/extra-manifest directory of the ztp-site-generate container, you can use extraManifests.searchPaths to include the path to the git directory containing those files. This allows the GitOps ZTP pipeline to apply those CR files during cluster installation. If you configure a searchPaths directory, the GitOps ZTP pipeline does not fetch manifests from the ztp-site-generate container during site installation.

  5. Generate the Day 0 installation CRs by processing the modified SiteConfig CR site-1-sno.yaml by running the following command:

    1. $ podman run -it --rm -v `pwd`/out/argocd/example/siteconfig:/resources:Z -v `pwd`/site-install:/output:Z,U registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4 generator install site-1-sno.yaml /output

    Example output

    1. site-install
    2. └── site-1-sno
    3.     ├── site-1_agentclusterinstall_example-sno.yaml
    4.     ├── site-1-sno_baremetalhost_example-node1.example.com.yaml
    5.     ├── site-1-sno_clusterdeployment_example-sno.yaml
    6.     ├── site-1-sno_configmap_example-sno.yaml
    7.     ├── site-1-sno_infraenv_example-sno.yaml
    8.     ├── site-1-sno_klusterletaddonconfig_example-sno.yaml
    9.     ├── site-1-sno_machineconfig_02-master-workload-partitioning.yaml
    10.     ├── site-1-sno_machineconfig_predefined-extra-manifests-master.yaml
    11.     ├── site-1-sno_machineconfig_predefined-extra-manifests-worker.yaml
    12.     ├── site-1-sno_managedcluster_example-sno.yaml
    13.     ├── site-1-sno_namespace_example-sno.yaml
    14.     └── site-1-sno_nmstateconfig_example-node1.example.com.yaml

  6. Optional: Generate just the Day 0 MachineConfig installation CRs for a particular cluster type by processing the reference SiteConfig CR with the -E option. For example, run the following commands:

    1. Create an output folder for the MachineConfig CRs:

      1. $ mkdir -p ./site-machineconfig

    2. Generate the MachineConfig installation CRs:

      1. $ podman run -it --rm -v `pwd`/out/argocd/example/siteconfig:/resources:Z -v `pwd`/site-machineconfig:/output:Z,U registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4 generator install -E site-1-sno.yaml /output

      Example output

      1. site-machineconfig
      2. └── site-1-sno
      3.     ├── site-1-sno_machineconfig_02-master-workload-partitioning.yaml
      4.     ├── site-1-sno_machineconfig_predefined-extra-manifests-master.yaml
      5.     └── site-1-sno_machineconfig_predefined-extra-manifests-worker.yaml

  7. Generate and export the Day 2 configuration CRs using the reference PolicyGenTemplate CRs from the previous step. Run the following commands:

    1. Create an output folder for the Day 2 CRs:

      1. $ mkdir -p ./ref

    2. Generate and export the Day 2 configuration CRs:

      1. $ podman run -it --rm -v `pwd`/out/argocd/example/policygentemplates:/resources:Z -v `pwd`/ref:/output:Z,U registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4 generator config -N . /output

      The command generates example group and site-specific PolicyGenTemplate CRs for single-node OpenShift, three-node clusters, and standard clusters in the ./ref folder.

      Example output

      1. ref
      2.  └── customResource
      3.       ├── common
      4.       ├── example-multinode-site
      5.       ├── example-sno
      6.       ├── group-du-3node
      7.       ├── group-du-3node-validator
      8.       │    └── Multiple-validatorCRs
      9.       ├── group-du-sno
      10.       ├── group-du-sno-validator
      11.       ├── group-du-standard
      12.       └── group-du-standard-validator
      13.            └── Multiple-validatorCRs

  8. Use the generated CRs as the basis for the CRs that you use to install the cluster. You apply the installation CRs to the hub cluster as described in “Installing a single managed cluster”. The configuration CRs can be applied to the cluster after cluster installation is complete.

Verification

  • Verify that the custom roles and labels are applied after the node is deployed:

    1. $ oc describe node example-node.example.com

Example output

  1. Name:   example-node.example.com
  2. Roles:  control-plane,example-label,master,worker
  3. Labels: beta.kubernetes.io/arch=amd64
  4.         beta.kubernetes.io/os=linux
  5.         custom-label/parameter1=true
  6.         kubernetes.io/arch=amd64
  7.         kubernetes.io/hostname=cnfdf03.telco5gran.eng.rdu2.redhat.com
  8.         kubernetes.io/os=linux
  9.         node-role.kubernetes.io/control-plane=
  10.         node-role.kubernetes.io/example-label= (1)
  11.         node-role.kubernetes.io/master=
  12.         node-role.kubernetes.io/worker=
  13.         node.openshift.io/os_id=rhcos
1The custom label is applied to the node.

Additional resources

Creating the managed bare-metal host secrets

Add the required Secret custom resources (CRs) for the managed bare-metal host to the hub cluster. You need a secret for the GitOps Zero Touch Provisioning (ZTP) pipeline to access the Baseboard Management Controller (BMC) and a secret for the assisted installer service to pull cluster installation images from the registry.

The secrets are referenced from the SiteConfig CR by name. The namespace must match the SiteConfig namespace.

Procedure

  1. Create a YAML secret file containing credentials for the host Baseboard Management Controller (BMC) and a pull secret required for installing OpenShift and all add-on cluster Operators:

    1. Save the following YAML as the file example-sno-secret.yaml:

      1. apiVersion: v1
      2. kind: Secret
      3. metadata:
      4.   name: example-sno-bmc-secret
      5.   namespace: example-sno (1)
      6. data: (2)
      7.   password: <base64_password>
      8.   username: <base64_username>
      9. type: Opaque
      10. ---
      11. apiVersion: v1
      12. kind: Secret
      13. metadata:
      14.   name: pull-secret
      15.   namespace: example-sno  (3)
      16. data:
      17.   .dockerconfigjson: <pull_secret> (4)
      18. type: kubernetes.io/dockerconfigjson
      1Must match the namespace configured in the related SiteConfig CR
      2Base64-encoded values for password and username
      3Must match the namespace configured in the related SiteConfig CR
      4Base64-encoded pull secret

  2. Add the relative path to example-sno-secret.yaml to the kustomization.yaml file that you use to install the cluster.

Configuring Discovery ISO kernel arguments for manual installations using GitOps ZTP

The GitOps Zero Touch Provisioning (ZTP) workflow uses the Discovery ISO as part of the OKD installation process on managed bare-metal hosts. You can edit the InfraEnv resource to specify kernel arguments for the Discovery ISO. This is useful for cluster installations with specific environmental requirements. For example, configure the rd.net.timeout.carrier kernel argument for the Discovery ISO to facilitate static networking for the cluster or to receive a DHCP address before downloading the root file system during installation.

In OKD 4, you can only add kernel arguments. You can not replace or delete kernel arguments.

Prerequisites

  • You have installed the OpenShift CLI (oc).

  • You have logged in to the hub cluster as a user with cluster-admin privileges.

  • You have manually generated the installation and configuration custom resources (CRs).

Procedure

  1. Edit the spec.kernelArguments specification in the InfraEnv CR to configure kernel arguments:
  1. apiVersion: agent-install.openshift.io/v1beta1
  2. kind: InfraEnv
  3. metadata:
  4.   name: <cluster_name>
  5.   namespace: <cluster_name>
  6. spec:
  7.   kernelArguments:
  8.     - operation: append (1)
  9.       value: audit=0 (2)
  10.     - operation: append
  11.       value: trace=1
  12.   clusterRef:
  13.     name: <cluster_name>
  14.     namespace: <cluster_name>
  15.   pullSecretRef:
  16.     name: pull-secret
1Specify the append operation to add a kernel argument.
2Specify the kernel argument you want to configure. This example configures the audit kernel argument and the trace kernel argument.

The SiteConfig CR generates the InfraEnv resource as part of the day-0 installation CRs.

Verification

To verify that the kernel arguments are applied, after the Discovery image verifies that OKD is ready for installation, you can SSH to the target host before the installation process begins. At that point, you can view the kernel arguments for the Discovery ISO in the /proc/cmdline file.

  1. Begin an SSH session with the target host:

    1. $ ssh -i /path/to/privatekey core@<host_name>

  2. View the system’s kernel arguments by using the following command:

    1. $ cat /proc/cmdline

Installing a single managed cluster

You can manually deploy a single managed cluster using the assisted service and Red Hat Advanced Cluster Management (RHACM).

Prerequisites

  • You have installed the OpenShift CLI (oc).

  • You have logged in to the hub cluster as a user with cluster-admin privileges.

  • You have created the baseboard management controller (BMC) Secret and the image pull-secret Secret custom resources (CRs). See “Creating the managed bare-metal host secrets” for details.

  • Your target bare-metal host meets the networking and hardware requirements for managed clusters.

Procedure

  1. Create a ClusterImageSet for each specific cluster version to be deployed, for example clusterImageSet-4.yaml. A ClusterImageSet has the following format:

    1. apiVersion: hive.openshift.io/v1
    2. kind: ClusterImageSet
    3. metadata:
    4.   name: openshift-4.0 (1)
    5. spec:
    6.    releaseImage: quay.io/openshift-release-dev/ocp-release:4.0-x86_64 (2)
    1The descriptive version that you want to deploy.
    2Specifies the releaseImage to deploy and determines the operating system image version. The discovery ISO is based on the image version as set by releaseImage, or the latest version if the exact version is unavailable.

  2. Apply the clusterImageSet CR:

    1. $ oc apply -f clusterImageSet-4.yaml

  3. Create the Namespace CR in the cluster-namespace.yaml file:

    1. apiVersion: v1
    2. kind: Namespace
    3. metadata:
    4.      name: <cluster_name> (1)
    5.      labels:
    6.         name: <cluster_name> (1)
    1The name of the managed cluster to provision.

  4. Apply the Namespace CR by running the following command:

    1. $ oc apply -f cluster-namespace.yaml

  5. Apply the generated day-0 CRs that you extracted from the ztp-site-generate container and customized to meet your requirements:

    1. $ oc apply -R ./site-install/site-sno-1

Additional resources

Monitoring the managed cluster installation status

Ensure that cluster provisioning was successful by checking the cluster status.

Prerequisites

  • All of the custom resources have been configured and provisioned, and the Agent custom resource is created on the hub for the managed cluster.

Procedure

  1. Check the status of the managed cluster:

    1. $ oc get managedcluster

    True indicates the managed cluster is ready.

  2. Check the agent status:

    1. $ oc get agent -n <cluster_name>

  3. Use the describe command to provide an in-depth description of the agent’s condition. Statuses to be aware of include BackendError, InputError, ValidationsFailing, InstallationFailed, and AgentIsConnected. These statuses are relevant to the Agent and AgentClusterInstall custom resources.

    1. $ oc describe agent -n <cluster_name>

  4. Check the cluster provisioning status:

    1. $ oc get agentclusterinstall -n <cluster_name>

  5. Use the describe command to provide an in-depth description of the cluster provisioning status:

    1. $ oc describe agentclusterinstall -n <cluster_name>

  6. Check the status of the managed cluster’s add-on services:

    1. $ oc get managedclusteraddon -n <cluster_name>

  7. Retrieve the authentication information of the kubeconfig file for the managed cluster:

    1. $ oc get secret -n <cluster_name> <cluster_name>-admin-kubeconfig -o jsonpath={.data.kubeconfig} | base64 -d > <directory>/<cluster_name>-kubeconfig

Troubleshooting the managed cluster

Use this procedure to diagnose any installation issues that might occur with the managed cluster.

Procedure

  1. Check the status of the managed cluster:

    1. $ oc get managedcluster

    Example output

    1. NAME            HUB ACCEPTED   MANAGED CLUSTER URLS   JOINED   AVAILABLE   AGE
    2. SNO-cluster     true                                   True     True      2d19h

    If the status in the AVAILABLE column is True, the managed cluster is being managed by the hub.

    If the status in the AVAILABLE column is Unknown, the managed cluster is not being managed by the hub. Use the following steps to continue checking to get more information.

  2. Check the AgentClusterInstall install status:

    1. $ oc get clusterdeployment -n <cluster_name>

    Example output

    1. NAME        PLATFORM            REGION   CLUSTERTYPE   INSTALLED    INFRAID    VERSION  POWERSTATE AGE
    2. Sno0026    agent-baremetal                               false                          Initialized
    3. 2d14h

    If the status in the INSTALLED column is false, the installation was unsuccessful.

  3. If the installation failed, enter the following command to review the status of the AgentClusterInstall resource:

    1. $ oc describe agentclusterinstall -n <cluster_name> <cluster_name>

  4. Resolve the errors and reset the cluster:

    1. Remove the cluster’s managed cluster resource:

      1. $ oc delete managedcluster <cluster_name>

    2. Remove the cluster’s namespace:

      1. $ oc delete namespace <cluster_name>

      This deletes all of the namespace-scoped custom resources created for this cluster. You must wait for the ManagedCluster CR deletion to complete before proceeding.

    3. Recreate the custom resources for the managed cluster.

RHACM generated cluster installation CRs reference

Red Hat Advanced Cluster Management (RHACM) supports deploying OKD on single-node clusters, three-node clusters, and standard clusters with a specific set of installation custom resources (CRs) that you generate using SiteConfig CRs for each site.

Every managed cluster has its own namespace, and all of the installation CRs except for ManagedCluster and ClusterImageSet are under that namespace. ManagedCluster and ClusterImageSet are cluster-scoped, not namespace-scoped. The namespace and the CR names match the cluster name.

The following table lists the installation CRs that are automatically applied by the RHACM assisted service when it installs clusters using the SiteConfig CRs that you configure.

Table 1. Cluster installation CRs generated by RHACM
CRDescriptionUsage

BareMetalHost

Contains the connection information for the Baseboard Management Controller (BMC) of the target bare-metal host.

Provides access to the BMC to load and start the discovery image on the target server by using the Redfish protocol.

InfraEnv

Contains information for installing OKD on the target bare-metal host.

Used with ClusterDeployment to generate the discovery ISO for the managed cluster.

AgentClusterInstall

Specifies details of the managed cluster configuration such as networking and the number of control plane nodes. Displays the cluster kubeconfig and credentials when the installation is complete.

Specifies the managed cluster configuration information and provides status during the installation of the cluster.

ClusterDeployment

References the AgentClusterInstall CR to use.

Used with InfraEnv to generate the discovery ISO for the managed cluster.

NMStateConfig

Provides network configuration information such as MAC address to IP mapping, DNS server, default route, and other network settings.

Sets up a static IP address for the managed cluster’s Kube API server.

Agent

Contains hardware information about the target bare-metal host.

Created automatically on the hub when the target machine’s discovery image boots.

ManagedCluster

When a cluster is managed by the hub, it must be imported and known. This Kubernetes object provides that interface.

The hub uses this resource to manage and show the status of managed clusters.

KlusterletAddonConfig

Contains the list of services provided by the hub to be deployed to the ManagedCluster resource.

Tells the hub which addon services to deploy to the ManagedCluster resource.

Namespace

Logical space for ManagedCluster resources existing on the hub. Unique per site.

Propagates resources to the ManagedCluster.

Secret

Two CRs are created: BMC Secret and Image Pull Secret.

  • BMC Secret authenticates into the target bare-metal host using its username and password.

  • Image Pull Secret contains authentication information for the OKD image installed on the target bare-metal host.

ClusterImageSet

Contains OKD image information such as the repository and image name.

Passed into resources to provide OKD images.