VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hi, I just found out what was wrong:I’m using a GitOps approach to declare the location and policy I did not see that Kasten modifies the provided yaml on the fly (adding lines such as receiveString) … and of course my GitOps controller - argocd - reverts those changesNow the question becomes: is there a best practice to declare k10 policies and locations using ArgoCD?
Yes, this is what I did for the time being (ignore syncing the policy resources).Looking forward for the results of your investigation. btw, on the usage of Kasten in GitOps paradigms I found the demo from Michael Cade very helpful: https://www.kasten.io/kubernetes/resources/videos/continuous-data-protection-with-kasten-k10-and-argocd (a topic to probably integrate in the Kasten k10 main documentation at some point?)
Hi guys,It looks like in version 5.5.7 the initial bug has been fixed as deployments now seem to be checking KanisterPodCustomAnnotations from in the k10-config configMap (replacing K with k makes the deployments fail so ...). That’s good news.Problem is that when I to add annotation sidecar.istio.io/inject=false (as in my case I’m using Istio service mesh) I cannot see that annotation on the kanister-job-* pods created and the istio proxy sidecar container is still injected.I also tried using the pod-spec-override to add the annotation but without much success.Ref to the documentation used: https://docs.kasten.io/latest/kanister/override.htmlWhat should I do to have the annotation actually added to the kanister-job pods?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.