vals-operator
vals-operator copied to clipboard
Kubernetes Operator to sync secrets between different secret backends and Kubernetes
Hi everyone, I've tried to configure vals-operator to use TLS authentication for connecting to Vault server but it doesn't seem to be working. Here is the piece of my values.yaml...
I tried using the templating for ValsSecret when I noticed that my CRDs which was installed with helm hasn't been updated. And after looking at the chart in this repo...
The change would allow the same secret to being synced to multiple namespaces. This can be very useful for secrets such as private docker registries. The new schema could look...
We currently support Postgres, MySQL and Cassandra over plain text. We need to add support for TLS as well.
Fixes #43
``` "level":"error","ts":"2024-02-06T11:06:48Z","logger":"controllers.vals-operator","msg":"Cannot parse template","error":"template: conf.yaml:1: bad character U+002D '-'","stacktrace":"digitalis.io/vals-operator/controllers.(*ValsSecretReconciler).Reconcile\n\t/workspace/controllers/valssecret_controller.go:203\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:316\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:227"} ```
is it doesn't support pulling values from aws ssm