shiftlaunch/example/config.yaml at main · IBM/shiftlaunch · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
# =============================================================================
# ShiftLaunch Master Configuration Reference
# Topology: Multi-Node Cluster
# Boot Method: Agent Installer (Recommended)
# =============================================================================

# -----------------------------------------------------------------------------
# 1. INFRASTRUCTURE SERVICES
# CONVENTION OVER CONFIGURATION:
# Core infrastructure services (DNS, Load Balancer, NFS) are automatically
# managed locally on the controller node if left commented out.
# To Bring Your Own Infrastructure (BYOI), simply uncomment the block
# and fill in your network target.
# -----------------------------------------------------------------------------
services:
  # --- CORE INFRASTRUCTURE (Managed locally by default if commented out) ---

  # dns:
    # external_nameserver: "192.168.100.5"  # Uncomment to bypass local dnsmasq and point to enterprise DNS

  # load_balancer:
    # vip: "192.168.100.50"                 # Uncomment to use a dedicated floating IP for the cluster
                                            # # or if you are planning to use this controller for managing multiple clusters
    # external_lb_ip: "192.168.100.2"       # Uncomment to bypass local HAProxy and route to an external F5/Big-IP

  # nfs:
    # external_nfs_server: "192.168.100.3"  # Uncomment to use an external enterprise NFS appliance for Agent ISOs
    # external_nfs_path: "/vol/shiftlaunch" # Required if external_nfs_server is used

  # --- BOOT METHOD SPECIFIC SERVICES ---
  # dhcp:
    #external_dhcp_server: "192.168.100.1"   # DHCP is inherently external for Agent ISO (uses NMState)

  # pxe:
    # external_pxe_server: "192.168.100.1"    # PXE is bypassed/not used for Agent ISO mode

  # --- BOUNDARY SERVICES (Strictly Opt-In; Stay completely off if commented out) ---

  # proxy:
    # external_http_proxy: "http://proxy.mycompany.com:8080"
    # external_https_proxy: "http://proxy.mycompany.com:8080"
    # no_proxy: "127.0.0.1,localhost,.example.local,192.168.100.0/24"
    # Note: To build a locally managed Squid proxy, simply use `proxy: {}`

  # registry:
    # external_registry_server: "registry.mycompany.com"
    # username: "admin"
    # password: "admin"
    # ca_cert_file: "/path/ca.crt"
    # Note: To build a locally managed Podman registry, simply use `registry: {}` (Requires air-gapped mode)

# -----------------------------------------------------------------------------
# 2. CORE NETWORK & ARCHITECTURE MODE
# -----------------------------------------------------------------------------
network:
  # ARCHITECTURE TARGETS:
  #   "connected"         -> Connected Installation (or Standard Connected Deployment). Nodes have direct outbound internet access.
  #   "restricted-network" -> Proxy-Connected or Restricted Network deployment. Nodes are isolated but access internet via Proxy gateway.
  #   "air-gapped"-> True Disconnected or Air-Gapped. Nodes are strictly airgapped. Enforces local Registry data.
  isolation_level: "connected"

  controller_interface: "eth0"             # Physical interface on the controller to bind the VIP and services to
  machine_network_cidr: "192.168.100.0/24" # The primary subnet the OpenShift nodes reside on
  gateway: "192.168.100.1"                 # The default gateway for the cluster nodes

  dns_forwarders:                          # Network DNS servers used by the local dnsmasq service
    - "8.8.8.8"
    - "1.1.1.1"

# -----------------------------------------------------------------------------
# 3. OPENSHIFT CLUSTER SETTINGS
# -----------------------------------------------------------------------------
openshift:
  cluster_name: "my-cluster"
  version: "4.21.18"
  release_type: "official"                 # "official" for stable releases, "ci" for raw nightly builds
  base_domain: "example.local"
  pull_secret_file: "~/pull-secret.json"
  ssh_public_key_file: "~/.ssh/id_rsa.pub"
  force_ocp_download: false                # Set to true to force re-download of existing OpenShift artifacts

# -----------------------------------------------------------------------------
# 4. HMC CREDENTIALS
# -----------------------------------------------------------------------------
hmc:
  ip: "192.168.100.10"
  username: "hscroot"
  password: "YOUR_HMC_PASSWORD"

# -----------------------------------------------------------------------------
# 5. NODE TOPOLOGY (HMC Target LPARs)
# -----------------------------------------------------------------------------
nodes:
  boot_method: "agent"                     # "agent" (ISO) or "netboot" (PXE)

  masters:
    - name: "master-0"
      ip: "192.168.100.12"
      existing_lpar_name: "my-master-0"
      system_name: "Power-System-1080-HEX"
    - name: "master-1"
      ip: "192.168.100.13"
      existing_lpar_name: "my-master-1"
      system_name: "Power-System-1080-HEX"
    - name: "master-2"
      ip: "192.168.100.14"
      existing_lpar_name: "my-master-2"
      system_name: "Power-System-1080-HEX"

  workers:
    - name: "worker-0"
      ip: "192.168.100.15"
      existing_lpar_name: "my-worker-0"
      system_name: "Power-System-1022-HEX"
    - name: "worker-1"
      ip: "192.168.100.16"
      existing_lpar_name: "my-worker-1"
      system_name: "Power-System-1022-HEX"