failed to apply k10.kasten.io/forcegenericbackup annotation on a specific deployments

Question

Hi,i have a customer where he has application “redis” who is controlled by redis-controller, the redis namespace have 3 deployments, and the csi driver does not support the volume snapshot so we go with generic backup.only one of the deployments get injected by kanister sidecar, and the remaining two did not, after troubleshooting we saw that the 2 deployments didnt accept the annotation:”k10.kasten.io/forcegenericbackup”, and it will be removed automatically after a few seconds.is there any possible way to inject kanister inside these deployments without adding this annotation?

Hagag · Accepted Answer

Hi @Ali KansoIt appears the customer is using a GitOps tool such as ArgoCD, Flux, or another continuous configuration tool, which reverts the changes back.The sidecar can be added either by leveraging K10's sidecar injection feature or by manually patching the resource ( as the cst is trying to achieve by using the annotation)you can ask the cst to try the other approach by enabling Kanister Sidecar Injection feature, please review the below linkhttps://docs.kasten.io/latest/install/generic.html?highlight=forcegenericbackup#enabling-kanister-sidecar-injectionAlso, i’d recommend reviewing the below End to End example.https://docs.kasten.io/latest/install/generic.html?highlight=forcegenericbackup#end-to-end-exampleThanksAhmed Hagag

Comment

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded