Skip to content

universal-application-openshift-node

Pipeline definition for individual OpenShift node deployment (agent-based install)

This profile defines the pipeline for deploying and configuring individual OpenShift nodes. It works in conjunction with the cluster pipeline to ensure proper node initialization and cluster integration.

This pipeline uses both agent-based installation where nodes boot from an agent image generated by the OpenShift installer and User Provisioned Infrastructure deployment of OpenShift nodes, meaning it uses Ignition for node configuration and does not rely on OpenShift's infrastructure management capabilities. The pipeline is designed to be flexible and can be customized based on specific requirements of the OpenShift node deployment.

When used with agent-based installs, the pipeline waits for the agent boot image to be ready and does not need to wait for the CSR approval as that is handled by the agent installation process. When used with Ignition-based installs, the pipeline waits for explicit CSR approval before proceeding with node initialization to ensure proper sequencing.

Requirements

  • Must be used with universal-application-openshift-cluster
  • CoreOS base OS requirements
  • Network connectivity to cluster
  • Proper role assignment (controlplane or worker)

Usage

This pipeline executes on each node with the following sequence:

Bash
# Node configuration:
- Applies CoreOS installation parameters based on node role
- Configures Ignition for node type
- Waits for cluster approval before proceeding
- Ensures proper node initialization order

The pipeline synchronizes node deployment with cluster formation by: - Waiting for cluster readiness signals - Applying role-specific configurations - Managing CoreOS installation - Coordinating cluster join operations

Objects that Reference universal-application-openshift-node

Not used in current content packs

Objects used by universal-application-openshift-node