We're using Werf to deploy the chart containing our app and Infisical operator/secrets, here's how we include it in Chart.yaml:
- name: secrets-operator
version: 0.10.7
repository: https://dl.cloudsmith.io/public/infisical/helm-charts/helm/charts/
condition: infisicalOperator.enabled
and in values.yaml of the chart it's enabled this way:
infisicalOperator:
enabled: true
We want the operator to be deployed before all the other deployments, so it'd sync secrets correctly. Werf allows it by adding the following annotation:
metadata:
annotations:
werf.io/weight: "-10"
so if we'd specify it as -10 for Infisical operator and 0 for the rest of the deployments, it'd apply the operator first, then wait until it's healthy, then deploy other services.
Problem is, as far as I've understood there's no way to specify the annotations that'd be applied globally to all operator services/deployments/etc.
The perfect solution would be allowing setting custom annotations via values.yaml so it'd be working correctly. Can this be done?
We're using Werf to deploy the chart containing our app and Infisical operator/secrets, here's how we include it in Chart.yaml:
and in values.yaml of the chart it's enabled this way:
We want the operator to be deployed before all the other deployments, so it'd sync secrets correctly. Werf allows it by adding the following annotation:
so if we'd specify it as -10 for Infisical operator and 0 for the rest of the deployments, it'd apply the operator first, then wait until it's healthy, then deploy other services.
Problem is, as far as I've understood there's no way to specify the annotations that'd be applied globally to all operator services/deployments/etc.
The perfect solution would be allowing setting custom annotations via values.yaml so it'd be working correctly. Can this be done?