Kubernetes API 1.22 migration

This article applies the https://kubernetes.io/docs/reference/using-api/deprecation-guide/ to the hivemq-operator Helm chart.

The v1.22 release stopped serving the v1beta1 deprecated API versions:

• admissionregistration.k8s.io/v1beta1 → admissionregistration.k8s.io/v1

• extensions/v1beta1 and networking.k8s.io/v1beta1 → networking.k8s.io/v1

• apiextensions.k8s.io/v1beta1 → apiextensions.k8s.io/v1

• etc.

The guide indicates to migrate manifests and API clients to use the v1 API version instead of v1beta1. You also must make changes to some values names and defaults.

\uD83D\uDCD8 Instructions

1. Get a local copy of the helm chart

   git clone https://github.com/hivemq/helm-charts.git
   cd helm-charts

2. Identify files that contain networking.k8s.io/v1beta1

   grep -R networking.k8s.io/v1beta1 .

3. Edit the ./charts/hivemq-swarm/templates/ingress.yaml. Update API version v1beta1 to v1:

   < apiVersion: networking.k8s.io/v1beta1
   ---
   > apiVersion: networking.k8s.io/v1

4. Update backend to defaultBackend and its keys from this:

     backend:
       serviceName: {{ $fullName }}-api
       servicePort: api

   to this:

     defaultBackend:
       service:
         name: {{ $fullName }}-api
         port:
           name: api

5. Add pathType to the path:

     - path: /
       pathType: ImplementationSpecific

All other YAML files already have depreciated API versions properly handled*. The patching is Done. Next step is to deploy the patched chart from the directory to a kubernetes cluster.

\uD83D\uDCD8 Deploy helm chart from a directory

1. Package the helm chart

   helm package ./helm-charts/charts/hivemq-operator \
     --dependency-update  \
     --destination result-dir
     
   Successfully packaged chart and saved it to: result-dir/hivemq-operator-0.11.5.tgz

2. Deploy the helm chart

   helm upgrade my-hivemq \
     --install result-dir/hivemq-operator-0.11.5.tgz 
     --values my-values.yaml

3. Done.

\uD83D\uDCCB Related articles