Question

Kasten kanisterPodCustomAnnotations does not seem to work

  • 26 February 2024
  • 1 comment
  • 125 views

Userlevel 2

Hi team,

 

We’re using Kasten version 6.5.1 for backing up our stateful resources on Kubernetes v1.26 (RKE2 distribution). Because we didn’t enable GSB (General Storage Backup) and our storage class is not CSI-compatible (local-path provisioner), we rely solely on Blueprints which trigger kanister pods with custom scripts to backup the workloads.

However, recently we introduced the service mesh (Linkerd) to our cluster and we did not want the kanister pods to receive an automatic proxy injection, as this makes the backup job dangling both in the cluster and in the UI. We don’t want to manually add the annotation enabling proxy to each workload either, as this introduces unnecessary overhead.

We’ve seen that it’s possible to set custom labels / annotations in Kanister documentation:

But both solutions yield no results. The `kanister-job-xxxx` pod from the Blueprints does not have any custom annotation, despite it being defined in our helm chart values:

The value is set both in the k10-config ConfigMap and as an environment variable KANISTER_POD_CUSTOM_ANNOTATIONS` in various k10-related deployments:

Additionally, we stumbled across the following thread: 

but there was no clear answer whether it’s working. Can someone provide us with an update if this functionality works as expected? If so, where are we making an error to achieve this?

Thanks in advance!


1 comment

Userlevel 4
Badge +2

Hello @peterturnip,

Thank you for using K10 community.

The correct option in this case would be to use custom annotations, since pod-spec-override is not intended to add annotations.

We are aware about kanisterPodCustomAnnotations and kanisterPodCustomLabels not being applied to kanister-job pods, and we will be working to fix this as soon as possible. The annotations and labels added in those fields are being applied to pods that runs on kasten-io namespace during the backup/export when using blueprints (i.e. datamover,copy-vol-data), but kanister-job pods runs on application's namespace.

I will update this thread as soon as we have the fix.

Also would like to recommend to keep an eye in our release pages where we will inform about new features and bug fixes.

https://docs.kasten.io/latest/releasenotes.html

Regards,
Rubens

Comment