/
upi-conf-vsphere-ref.yaml
41 lines (41 loc) · 1.55 KB
/
upi-conf-vsphere-ref.yaml
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
ref:
as: upi-conf-vsphere
from: upi-installer
grace_period: 10m
commands: upi-conf-vsphere-commands.sh
env:
- name: FIPS_ENABLED
default: "false"
documentation: "Indicates a FIPS-enabled cluster, to disable FIPS host checks in the installer."
- name: CONTROL_PLANE_REPLICAS
default: "3"
documentation: |-
the number of the master nodes for upi on vsphere cluster.
- name: COMPUTE_NODE_REPLICAS
default: "3"
documentation: |-
the number of the worker nodes for upi on vsphere cluster.
credentials:
- namespace: test-credentials
name: vsphere-vmc
mount_path: /var/run/vault/vsphere
- namespace: test-credentials
name: ci-ibmcloud
mount_path: /var/run/vault/ibmcloud
- namespace: test-credentials
name: vsphere-config
mount_path: /var/run/vault/vsphere-config
resources:
requests:
cpu: 10m
memory: 100Mi
dependencies:
- name: "release:latest"
env: OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE
- name: "release:latest"
env: RELEASE_IMAGE_LATEST
documentation: >-
This step creates the files necessary to deploy a vSphere UPI cluster.
It requires an existing install-config.yaml to exist in the shared directory with the necessary configuration to deploy a cluster to the vSphere CI project.
It uses this install-config.yaml to generate the govc.sh, Ignition, metadata.json, and kubeconfig files with the modifications required to support the vSphere UPI workflow.
These files are copied to the shared directory for future consumption.