Open saksmt opened 2 months ago
Thank you for your contribution! This issue has been automatically marked as stale
because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale
label will be automatically removed.
Preflight Checklist
Operator Version
1.22.1
Installation Type
Official Helm chart
Bank-Vaults Version
No response
Kubernetes Version
1.27.3
Kubernetes Distribution/Provisioner
kind
Expected Behavior
Vault configurer is up and running, accepting
vault_cr
labeled config maps and kv v2 atplatform/secrets
is eventually created.Actual Behavior
No vault configurer is deployed, nothing listens for config maps and no errors or warnings are reported anywhere.
Steps To Reproduce
vault-root
), namespace -security-vault
kubectl apply
provided yaml (note missingexternalConfig
field!)Configuration
Logs
Additional Information
This check is frustratingly difficult to figure out and debug. It is poorly documented and is very questionable why such behavior even exists.
Motivation: by default one would expect that not providing any
externalConfig
in vault CR would leave one with working vault instance that can be further customized in a decoupled way via config maps. But that assumption is incorrect and it is not documented (wholevault_cr
stuff is really can be figured out through digging through examples, but that is another issue entirely) anywhere.