Parameters

The parent key for all the following parameters is openshift4_config.

`globalPullSecret`

type	string
default	absent

This parameter is deprecated. Please migrate your additional pull secrets to parameter globalPullSecrets.

A Vault reference pointing to the Vault secret containing the docker configuration file in JSON format. If the parameter is null, the component doesn’t manage the cluster’s global pull secret.

The component writes the value of this parameter into the field .dockerconfigjson of the secret pull-secret in namespace openshift-config.

See the OpenShift documentation for more details on managing the cluster’s global pull secret.

You need to make sure that the existing pull secrets present on a cluster (deployed by the OpenShift installer) are included in the configuration deployed by this component. Otherwise, OpenShift cluster services may stop working because their respective container images can’t be downloaded anymore.

`globalPullSecrets`

type

dict

default

{}

example

docker.io:
  email: dockerhub@example.com (1)
  auth: ?{vaultkv:${cluster:tenant}/${cluster:name}/openshift4-config/docker.io-pull-secret} (2)

1	Some registries require an email address to be present for authenticated pulls.
2	We strongly recommend that you store the `auth` value for the registry in Vault.

This parameter allows customizing the OpenShift cluster pull-secret without having to replicate the complete secret contents in Vault. The component expects entries in the dict to be valid entries for the .dockerconfigjson auths field. The component allows users to remove existing entries (also entries originally created by the OpenShift installer) by setting the value for a registry host to null.

The component doesn’t base64-encode the value provided for auth. Please make sure that you store the auth value as base64 in Vault.

`clusterUpgradeSCCPermissionFix`

type	dictionary

If enabled fixes cluster upgrades on 4.10 clusters with custom SCCs that set privileged: true. A copy of the default privileged SCC is created with increased priority to be chosen over custom SCCs.

`clusterUpgradeSCCPermissionFix.enabled`

type	boolean
default	`true`

Whether to enable the SCC priority fix.

`clusterUpgradeSCCPermissionFix.priority`

type	number
default	`3`

The priority the resulting SCC will have.