Skip to content
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

PodDisruptionBudget policy/v1beta1 removed in v1.25+ #1475

Closed
bdols opened this issue Aug 11, 2023 · 2 comments · Fixed by #1476
Closed

PodDisruptionBudget policy/v1beta1 removed in v1.25+ #1475

bdols opened this issue Aug 11, 2023 · 2 comments · Fixed by #1476

Comments

@bdols
Copy link
Contributor

bdols commented Aug 11, 2023

Describe the bug

The helm charts for loadtester and flagger are not installable in v1.25 when podDisruptionBudgets are set due to the removal of the policy/v1beta1 API version

To Reproduce

set podDisruptionBudget.enabled=true when installing the charts on new clusters.

Expected behavior

PDBs installed using the policy/v1 API version

Additional context

  • Flagger version: 1.32.0
  • Kubernetes version: v1.25
  • Service Mesh provider: linkerd
  • Ingress provider: nginx
@frankjkelly
Copy link

Thanks @bdols and @stefanprodan - any word on when this might be released? We are moving to EKS 1.25 in the coming week.

@bdols
Copy link
Contributor Author

bdols commented Aug 28, 2023

I can't speak to when this will be released @frankjkelly but you could use a kustomization to render the PDB outside of the helm install as a workaround in the meantime (assuming that you are using Flux to deploy helm charts). Like how a namespace is created in the resources pulled in here: https://github.com/fluxcd/flux2-kustomize-helm-example/blob/main/infrastructure/controllers/kustomization.yaml
I add resources to the kustomization.yaml that published helm charts don't support such as HPA's, multiple ingress, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants