openshift/extra-manifests¶
List of DRP templates to render as extra OpenShift manifests during cluster creation
This parameter defines a list of DRP template names that will be rendered and
written to the /root/cluster/openshift/ directory before openshift-install
agent create pxe-files runs. Any valid OpenShift manifest can be injected
this way — MachineConfigs, Secrets, ConfigMaps, operator configs, etc.
Each template is rendered against the cluster machine context, so it has
access to all cluster parameters via the standard DRP template functions
(.Param, .ParamExpand, .ParamComposeExpand, etc.).
The rendered output is written to a file named after the template
(e.g., my-machineconfig.yaml.tmpl produces my-machineconfig.yaml).
Requirements¶
- Each template must exist in the DRP content bundle
- Each template must produce valid YAML when rendered
Usage¶
openshift/extra-manifests:
- machineconfig-disable-auto-dhcp.yaml.tmpl
- machineconfig-custom-kubelet.yaml.tmpl
- configmap-cluster-monitoring.yaml.tmpl
Example: Disable NetworkManager Auto-DHCP¶
Create a template machineconfig-disable-auto-dhcp.yaml.tmpl:
---
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
labels:
machineconfiguration.openshift.io/role: worker
name: 99-worker-disable-auto-dhcp
spec:
config:
ignition:
version: 3.2.0
storage:
files:
- contents:
source: data:,%5Bmain%5D%0Ano-auto-default%3D%2A%0A
mode: 420
path: /etc/NetworkManager/conf.d/no-auto-default.conf
Then add it to the cluster profile:
Objects that Reference openshift/extra-manifests¶
- templates openshift-cluster-join.sh.tmpl in Openshift as part of Contents (used)
Objects used by openshift/extra-manifests¶
Not used in current content packs