Installing Db2 Operator V2

You can install the Db2 Operator V2 by using Helm through the command line.

helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm

helm template db2-operator-cluster-scoped ibm-helm/db2-operator-cluster-scoped  \
  --set global.operatorNamespace="${OPERATOR_NAMESPACE}" \
  | ${KCTL} apply -f -

helm upgrade --install db2-operator ibm-helm/db2-operator-standalone \
  --namespace "${OPERATOR_NAMESPACE}" \
  -f overrides.yaml \
  --set db2u.operator.image.tag="${OPERATOR_TAG}"

To install the Db2 Operator V2

1. Verify that cert-manager is installed and running in the cluster:

   ${KCTL} get pods -n cert-manager

   1. If no cert-manager pods are found, install cert-manager. For more information, see Installation. For example:

      ${KCTL} apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.18.2/cert-manager.yaml

2. Set the following environment variables:

   For Red Hat Openshift

   export KCTL=oc 
   export OPERATOR_NAMESPACE=db2-operator 
   export OPERATOR_TAG=v2.0.0 
   export ENTITLEMENT_KEY=<your-entitlement-key>

   For Kubernetes

   export KCTL=kubectl 
   export OPERATOR_NAMESPACE=db2-operator 
   export OPERATOR_TAG=v2.0.0 
   export ENTITLEMENT_KEY=<your-entitlement-key>

   Where <your-entitlement-key> is your IBM Entitlement Key.
3. Create the namespace where you want to install the operator:

   ${KCTL} create namespace "${OPERATOR_NAMESPACE}" 
   

4. Create an image pull secret in the operator namespace to authenticate with the IBM Container Registry:

   ${KCTL} -n "${OPERATOR_NAMESPACE}" create secret docker-registry ibm-entitlement-key \ 
     --docker-server=icr.io \ 
     --docker-username=cp \ 
     --docker-password="${ENTITLEMENT_KEY}" 
   

5. Create a values file named overrides.yaml with your installation configuration:

   global: 
     metaNamespace: $OPERATOR_NAMESPACE 
     licenseAccept: true 

   If you are using a Kubernetes cluster, add the following platform setting:

   db2u: platform: K8S

   Note: The global.metaNamespace field specifies the namespace where the operator is installed. If global.watchNamespace is not set, the operator watches only its own namespace. In this default configuration, create Db2uInstance resources in the operator namespace.
   1. If you have a deployment with a large number of nodes and partitions, such as those in IBM CloudRack, increase the resources allocated to the operator by adding the following resources section to the overrides.yaml:

      global: 
        metaNamespace: $OPERATOR_NAMESPACE 
        imagePullPrefix: icr.io/db2u 
        licenseAccept: true 
       
      db2u:
        resources:
          limits:
            cpu: 1
            memory: 1000Mi
          requests:
            cpu: 500m
            memory: 500Mi

6. Install the cluster-scoped resources by using the helm template and applying the rendered manifests:

   helm template db2-operator-cluster-scoped ./charts/db2-operator-cluster-scoped \
     --set global.operatorNamespace="${OPERATOR_NAMESPACE}" \
     | ${KCTL} apply -f -

   Important: Do not install the db2-operator-cluster-scoped chart as a Helm release. Use helm template and kubectl apply to install these resources independently of the operator release.
7. Install the operator by using the standalone chart:

   helm upgrade --install db2-operator ./db2-operator-standalone \
     --namespace "${OPERATOR_NAMESPACE}" \
     -f overrides.yaml \
     --set db2u.operator.image.tag="${OPERATOR_TAG}"
   

8. Verify the installation:
   1. Run the following command to verify that the operator deployment is available:

      ${KCTL} wait deployment/db2-database-operator-controller-manager \
        -n "${OPERATOR_NAMESPACE}" \
        --for=condition=Available \
        --timeout=300s

      The command returns when the deployment becomes available
   2. Run the following command to check the operator pods:

      ${KCTL} get pods -n "${OPERATOR_NAMESPACE}"

      The operator pod should be in a Running state with all containers ready.
   3. Run the following commands to check the operator logs:

      ${KCTL} logs -n "${OPERATOR_NAMESPACE}" \
        deployment/db2-database-operator-controller-manager \
        -c manager

      The logs should show normal startup and reconciliation activity.
9. Optionally, you can configure the operator to watch multiple namespaces:
   1. Override the global.watchNamespace field in your values file:

      global: 
        watchNamespace: 
          - db2-team-a 
          - db2-team-b 
          - db2-team-c 
      

   2. Upgrade the operator release:

      helm upgrade db2-operator ./charts/db2-operator-standalone \ 
        --namespace "${OPERATOR_NAMESPACE}" \ 
        -f overrides.yaml \ 
        --set db2u.operator.image.tag="${OPERATOR_TAG}"

      Note: The operator automatically includes its own namespace in the watch list. You do not need to add the operator namespace to global.watchNamespace.