Upgrading Postgres data store on Linux on Power (ppc64le)

Complete these steps to upgrade Postgres data store.

1. If you are upgrading Postgres on a Red Hat OpenShift cluster, determine the file system group ID from the instana-postgres namespace. Red Hat OpenShift requires that file system groups are within a range of values specific to the namespace.

   kubectl get namespace instana-postgres -o yaml
    

   An output similar to the following example is shown for the command:

   apiVersion: v1
   kind: Namespace
   metadata:
   annotations:
     .......
     openshift.io/sa.scc.uid-range: 1000750000/10000
     creationTimestamp: "2024-01-14T07:04:59Z"
   labels:
     kubernetes.io/metadata.name: instana-postgres
     .......
     name: instana-postgres
    

   The openshift.io/sa.scc.supplemental-groups annotation contains the range of allowed IDs. The range 1000750000/10000 indicates 10,000 values starting with ID 1000750000, so it specifies the range of IDs from 1000750000 to 1000760000. In this example, the value 1000750000 might be used as a file system group ID (UID).

2. Upgrade the Postgres operator.

   helm upgrade --install cnpg instana/cloudnative-pg \
     --set image.repository=artifact-public.instana.io/self-hosted-images/3rd-party/operator/cloudnative-pg \
     --set image.tag=v1.29.1_v0.34.0 \
     --version=0.28.2 \
     --set imagePullSecrets[0].name=instana-registry \
     --set containerSecurityContext.runAsUser=<UID from namespace> \
     --set containerSecurityContext.runAsGroup=<UID from namespace> \
     -n instana-postgres
    

3. Update the Postgres cluster resource by applying the following patch:

   kubectl patch cluster postgres -n instana-postgres --type=merge --patch '
   spec:
     imageName: artifact-public.instana.io/self-hosted-images/3rd-party/datastore/cnpg-containers:15_v0.40.0
   '
    

4. Complete the steps in Verifying Postgres (online and offline).

To upgrade Zalando Postgres operator online, complete the following steps:

1. Create a file, for example values.yaml, with the Postgres configuration.

   configGeneral:
     kubernetes_use_configmaps: true
   securityContext:
     runAsUser: 101
   image:
     registry: artifact-public.instana.io
     repository: self-hosted-images/3rd-party/operator/zalando
     tag: "v1.10.0_v0.1.0"
   imagePullSecrets:
     - name: instana-registry
   configKubernetes:
     pod_service_account_definition: |
       apiVersion: v1
       kind: ServiceAccount
       metadata:
         name: postgres-pod
       imagePullSecrets:
         - name: instana-registry
   podServiceAccount:
     name: postgres-pod
    

2. Upgrade the Postgres operator.

   helm upgrade --install postgres-operator instana/postgres-operator \
     --version=v1.10.1 \
     -f values.yaml \
     -n instana-postgres
    

3. Update the Postgres cluster resource by applying the following patch:

   kubectl patch postgresql postgres -n instana-postgres --type=merge --patch '
   spec:
     dockerImage: artifact-public.instana.io/self-hosted-images/3rd-party/datastore/zalando:15.7_v0.1.0
   '
    

4. Complete the steps in Verifying Postgres (online and offline).

If you didn't yet pull the Postgres images from the external registry, you can pull them now. Run the following commands on your bastion host. Then, copy the images to your Instana host that is in your air-gapped environment.

docker pull artifact-public.instana.io/self-hosted-images/3rd-party/operator/cloudnative-pg:v1.29.1_v0.34.0
docker pull artifact-public.instana.io/self-hosted-images/3rd-party/datastore/cnpg-containers:15_v0.39.0
            

Complete the following steps on your Instana host.

1. Retag the images to your internal image registry.

   docker tag artifact-public.instana.io/self-hosted-images/3rd-party/operator/cloudnative-pg:v1.29.1_v0.34.0 <internal-image-registry>/operator/cloudnative-pg:v1.29.1_v0.34.0
   docker tag artifact-public.instana.io/self-hosted-images/3rd-party/datastore/cnpg-containers:15_v0.39.0 <internal-image-registry>/datastore/cnpg-containers:15_v0.39.0
                     

2. Push the images to your internal image registry on your bastion host.

   docker push <internal-image-registry>/operator/cloudnative-pg:v1.29.1_v0.34.0
   docker push <internal-image-registry>/datastore/cnpg-containers:15_v0.39.0
                     

3. If you are upgrading Postgres on a Red Hat OpenShift cluster, determine the file system group ID from the instana-postgres namespace. Red Hat OpenShift requires that file system groups are within a range of values specific to the namespace.

   kubectl get namespace instana-postgres -o yaml
    

   An output similar to the following example is shown for the command:

   apiVersion: v1
   kind: Namespace
   metadata:
   annotations:
     .......
     openshift.io/sa.scc.uid-range: 1000750000/10000
     creationTimestamp: "2024-01-14T07:04:59Z"
   labels:
     kubernetes.io/metadata.name: instana-postgres
     .......
     name: instana-postgres
    

   The openshift.io/sa.scc.supplemental-groups annotation contains the range of allowed IDs. The range 1000750000/10000 indicates 10,000 values starting with ID 1000750000, so it specifies the range of IDs from 1000750000 to 1000760000. In this example, the value 1000750000 might be used as a file system group ID (UID).

4. Upgrade the Postgres operator. In the following command, update the <download_key> value with your own agent key. If you created an image pull secret for your internal registry, add --docker-server=<internal-image-registry>:<internal-image-registry-port> to the following command.

   • Red Hat OpenShift cluster

     Use the UID from the previous step as the <UID from namespace> in the following commands:

     helm upgrade --install cnpg cloudnative-pg-1.28.0.tgz --set image.repository=<internal-image-registry>/instana-postgres/cloudnative-pg-operator -set image.tag=v1.29.1_v0.34.0 --version=0.28.2 --set containerSecurityContext.runAsUser=<UID from namespace> --set containerSecurityContext.runAsGroup=<UID from namespace> -n instana-postgres
      

   • Kubernetes cluster

     helm upgrade --install cnpg cloudnative-pg-0.28.2.tgz --set image.repository=<internal-image-registry>/operator/cloudnative-pg --set image.tag=v1.29.1_v0.34.0 --version=0.28.2 -n instana-postgres
      

5. Upgrade Postgres by running to the following command to patch Postgres custom resource.

   kubectl patch cluster postgres -n instana-postgres --type=merge --patch '
   spec:
     imageName: <internal-image-registry>/self-hosted-images/3rd-party/datastore/cnpg-containers:15_v0.40.0
     '
    

6. Complete the steps in Verifying Postgres (online and offline).

If you are using a Red Hat OpenShift cluster, create Security Context Constraints before you deploy the Postgres operator.

1. Update the YAML file, for example postgres-scc.yaml, with the SCC resource definition.

   apiVersion: security.openshift.io/v1
   kind: SecurityContextConstraints
   metadata:
     name: postgres-scc
   runAsUser:
     type: MustRunAs
     uid: 101
   seLinuxContext:
     type: RunAsAny
   fsGroup:
     type: RunAsAny
   allowHostDirVolumePlugin: false
   allowHostNetwork: true
   allowHostPorts: true
   allowPrivilegedContainer: false
   allowHostIPC: true
   allowHostPID: true
   readOnlyRootFilesystem: false
   users:
     - system:serviceaccount:instana-postgres:postgres-operator
     - system:serviceaccount:instana-postgres:postgres-pod
     - system:serviceaccount:instana-postgres:default
    

Then, proceed with upgrading the Postgres operator.

If you didn't yet pull the Postgres images from the external registry, you can pull them now. Run the following commands on your bastion host. Then, copy the images to your Instana host that is in your air-gapped environment.

docker pull artifact-public.instana.io/self-hosted-images/3rd-party/operator/zalando:v1.10.0_v0.1.0
docker pull artifact-public.instana.io/self-hosted-images/3rd-party/datastore/zalando:15.7_v0.1.0
            

Complete the following steps on your Instana host.

1. Retag the images to your internal image registry.

   docker tag artifact-public.instana.io/self-hosted-images/3rd-party/operator/zalando:v1.10.0_v0.1.0 <internal-image-registry>/self-hosted-images/3rd-party/operator/zalando:v1.10.0_v0.1.0
   docker tag artifact-public.instana.io/self-hosted-images/3rd-party/datastore/zalando:15.7_v0.1.0 <internal-image-registry>/self-hosted-images/3rd-party/datastore/zalando:15.7_v0.1.0
                     

2. Push the images to your internal image registry on your bastion host.

   docker push <internal-image-registry>/self-hosted-images/3rd-party/operator/zalando:v1.10.0_v0.1.0
   docker push <internal-image-registry>/self-hosted-images/3rd-party/datastore/zalando:15.7_v0.1.0
                     

3. Update the YAML file, for example values.yaml, with the Postgres configuration.

   configGeneral:
   kubernetes_use_configmaps: true
   securityContext:
   runAsUser: 101
   image:
   registry: <internal-image-registry>
   repository: self-hosted-images/3rd-party/operator/zalando
   tag: "v1.10.0_v0.1.0" 
   imagePullSecrets:
   - name: instana-registry
   configKubernetes:
   pod_service_account_definition: |
    apiVersion: v1
    kind: ServiceAccount
    metadata:
      name: postgres-pod
    imagePullSecrets:
      - name: instana-registry
   podServiceAccount:
   name: postgres-pod
    

4. Upgrade the Postgres operator. If you created an image pull secret in the previous step, add --set imagePullSecrets[0].name="<internal-image-registry-pull-secret>" to the following command.

   helm upgrade --install postgres-operator postgres-operator-ppc64le-1.10.0.tgz \
     --version=1.10.0 \
     --set configGeneral.kubernetes_use_configmaps=true \
     --set securityContext.runAsUser=101 \
     --namespace=instana-postgres \
     --set image.registry=<internal-image-registry> \
     --set image.repository=ppc64le-oss/postgres-operator-ppc64le \
     --set image.tag=v1.10.0_v0.1.0
                     

5. Upgrade Postgres by running the following command to patch Postgres custom resource.

   kubectl patch postgresql postgres -n instana-postgres --type=merge --patch '
   spec:
     dockerImage: <internal-image-registry>/self-hosted-images/3rd-party/datastore/zalando:15.7_v0.1.0
   '
    

6. Complete the steps in Verifying Postgres (online and offline).