-
Notifications
You must be signed in to change notification settings - Fork 1.9k
changed PodDisruptionBudget to policy/v1 because it's failing in k8s version 1.21.2 #1453
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
It should be changed to something like
so that it did not break on |
Hi @shubham-automation, Thanks for opening this PR. |
Hi @jmlrt , in my case |
@ebuildy how do you use helm? For templating or while interacting with a running cluster? |
I have understood, we use argoCD with Helm v3.8 to deploy against a cluster k8s v1.19. This is a wrong set!
As such, Helm questions helm/helm#10760 |
In our elastic helm-chart fork, I have replaced this by bitnami solution that rely on apiVersion: https://github.com/bitnami/charts/blob/master/bitnami/common/templates/_capabilities.tpl#L21
|
${CHART}/tests/*.py
${CHART}/examples/*/test/goss.yaml