Skip to main content
Version: Release 22.2

Change Parameters From the CR or Deployment

This topic describes how to customize the CR file or the operator deployment.

Change parameters in the CR

The custom resource should be on the cluster under CRD digitalaireleases.xlr.digital.ai (or digitalaireleaseocps.xlrocp.digital.ai for OpenShift)

❯ kubectl get crd
NAME CREATED AT
...
digitalaireleases.xlr.digital.ai 2022-06-20T12:35:09Z
...

❯ kubectl get digitalaireleases.xlr.digital.ai -n custom-namespace-1
NAME AGE
dai-xlr-custom-namespace-1 4h33m

You can change the CR dai-xlr-custom-namespace-1 by editing the CR on the cluster, for example

❯ kubectl edit digitalaireleases.xlr.digital.ai dai-xlr-custom-namespace-1 -n custom-namespace-1

Or you can edit the file that was used during installation, for example digitalai-release/kubernetes/dairelease_cr.yaml:

❯ kubectl apply -f digitalai-release/kubernetes/dairelease_cr.yaml -n custom-namespace-1

After changes are applied on the cluster, if the parameters are related to the release pods you need to restart release statefulset:

❯ kubectl rollout restart dai-xlr-custom-namespace-1-digitalai-release -n custom-namespace-1

Change parameters in the operator deployment

The operator deployment should be on the cluster in the namespace with name xlr-operator-controller-manager:

❯ kubectl get deployment -n custom-namespace-1
NAME READY UP-TO-DATE AVAILABLE AGE
dai-xlr-1234567890-nginx-ingress-controller 1/1 1 1 4h8m
dai-xlr-1234567890-nginx-ingress-controller-default-backend 1/1 1 1 4h8m
xlr-operator-controller-manager 1/1 1 1 3d5h

By changing that resource you can update:

  • the version of the operator image (do this only in case that you know there are no major changes in the operator image, contact support)
  • update operator resources under the path spec.template.spec.containers[1].resources

You can change the deployment xlr-operator-controller-manager by editing the deployment on the cluster, for example

❯ kubectl edit deployment xlr-operator-controller-manager -n custom-namespace-1

Or you can edit the file that was used during installation, for example digitalai-release/kubernetes/template/deployment.yaml:

❯ kubectl apply -f digitalai-release/kubernetes/template/deployment.yaml -n custom-namespace-1

After changes are applied on the cluster there should be also visible.