-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm chart is missing capabilities config #387
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
We had the same issue, we found that setting replicacount to more than 1 ie: 2,3 and so on. Will give you this issue. Since this is just the operator and not vault itself. Set it to 1 should fix your issue. |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
May 5, 2024
Ping. |
csatib02
removed
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
May 6, 2024
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Jul 7, 2024
csatib02
added
good first issue
Good for newcomers
and removed
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
good first issue
Good for newcomers
labels
Jul 28, 2024
Fixed by: #527 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Preflight Checklist
Operator Version
v1.21.2
Installation Type
Official Helm chart
Bank-Vaults Version
v1.31.0
Kubernetes Version
1.27.0
Kubernetes Distribution/Provisioner
GKE
Expected Behavior
PDB template has been added recently https://github.com/bank-vaults/vault-operator/pull/324/files and it should works.
Actual Behavior
However, I see the error with PDB template
I believe this
common.capabilities.policy.apiVersion
should be define in_helpers.tpl
or separate file_capabilities.tpl
or inchart.yaml
as dependence but it doesn't.Kindly ask if someone can have a look?
The text was updated successfully, but these errors were encountered: