Configuration properties in the values.yaml file for deploying the IBM App Connect Operator

Kubernetes-only content The values.yaml file for the Helm chart defines configuration properties and values that are used to deploy the IBM® App Connect Operator in your cluster. You can update the values.yaml file before you run the helm install command to install the Operator. Alternatively, you can retain the default values in values.yaml and instead use the --set flag (with individual parameters) to apply overrides when you run helm install.

The file is stored in the following location: /ibm-appconnect-operator/values.yaml.

The following configuration properties are defined in the values.yaml file.

Configuration property	Type	Default	Description
`namespace`	string	"appconnect"	The namespace to which you want to deploy the IBM App Connect Operator.
`operator.deployment.image`	string	"appconnect-operator"	The IBM App Connect Operator image name.
`operator.deployment.nodeSelector`	object	{}	A set of key/value pairs that must be matched against the node labels to decide whether the IBM App Connect Operator pod can be scheduled on that node. Only nodes matching all of these key/value pairs in their labels will be selected for scheduling the pod. Specify these settings as a JSON object in the format `key: value`. Example: `{workloadType: ace}` For more information, see nodeSelector and Assign Pods to Nodes in the Kubernetes documentation.
`operator.deployment.pullPolicy`	string	"Always"	The pull policy for the IBM App Connect Operator image, which determines when to pull the image from the registry. The valid values are as follows: `Always`: Queries the image registry whenever a container is launched to determine whether to use a locally cached image (with an identical image digest), or to pull an image with a new digest. `IfNotPresent`: Pulls the image only if it is not already present locally. `Never`: Makes no attempt to fetch the image typically because the image is assumed to exist locally.
`operator.deployment.repository`	string	"icr.io/cpopen"	The remote repository from which to pull the IBM App Connect Operator image. If the IBM App Connect Operator image is saved to a private registry (for example, in an air-gapped environment), `operator.deployment.repository` and `operator.privateRegistry` typically point to the same registry.
`operator.deployment.resources`	object	{"limits":{"ephemeral-storage":"512Mi","memory":"1Gi"},"requests":{"cpu":"100m","ephemeral-storage":"50Mi","memory":"128Mi"}}	Resource limits to apply to the IBM App Connect Operator pod.
`operator.deployment.sha`	string	sha256:77e1461f0e113a9f18b71ae65177f350f427bea6a8b913aabfb8794a1a7991ea	The SHA value of the IBM App Connect Operator image.
`operator.deployment.tag`	string		A tag value for the IBM App Connect Operator image. This value is optional and is ignored if you supply a SHA value.
`operator.deployment.tolerations`	array	[]	One or more tolerations to prevent the IBM App Connect Operator pod from being scheduled on inappropriate nodes. First, apply one or more taints to a node (by running kubectl taint with a key, value, and taint effect) to indicate that the node should repel any pods that do not tolerate the taints. Then, use the `operator.deployment.tolerations` property to apply toleration settings (`effect`, `key`, `operator`, `tolerationSeconds`, and `value`) to the pod to allow it to be scheduled on the node if the pod's toleration matches the node's taint. Specify these settings as a JSON array. Example: `[{key: "workloadType", operator: "Equal", value: "ace", effect: "NoSchedule"}]` For more information, see Taints and Tolerations in the Kubernetes documentation.
`operator.env`	object	{}	Environment variables that you want to pass to the IBM App Connect Operator pod to expose pod information to containers that are running in the pod. Specify these variables in the format `key: "value"`. Example: `{MY_ENV_VAR1: "value2",MY_ENV_VAR2: "value2"}`
`operator.imagePullSecrets`	list	[]	A comma-separated list of pull secrets that allow pulling images from authenticated registries.
`operator.installMode`	string	"OwnNamespace"	The installation mode for the IBM App Connect Operator, which determines the scope at which it operates. The valid values are as follows: `OwnNamespace`: The Operator is deployed into the specified namespace and can manage App Connect instances in that namespace only. `AllNamespaces`: The Operator is deployed into the specified namespace and can manage App Connect instances in any namespace.
`operator.privateRegistry`	string	""	A private registry override that allows pulling from alternative private registries.
`operator.replicas`	int	1	The number of replicas for the IBM App Connect Operator pod. The recommended number is 1.