fluxcd/flagger

PodDisruptionBudget - Feature request to be managed by Flagger

AshDerTest opened this issue · 1 comments

Describe the feature

Currently with PDB creation, the selector labels are used to determine the pods being monitored.
When Flagger deploys the {app.kubernetes.io/name:} is updated to have -primary attached to the end.
Is it possible to get Flagger to manage the PDD and create a Primary version.

Proposed solution

Add section in canary yaml in flagger

spec:
targetRef:
apiVersion: apps/v1
kind: Deployment
name: myapp-primary

other configuration options for Flagger

podDisruptionBudget:
name: myapp-pdb
enabled: true

to monitor and maintain the PDB

Any alternatives you've considered?

  • Would require a new set of selector labels (using helm)
  • Manul scripts not ideal

Can you describe in more detail your thoughts on this part of the Pod labels change or label selector change in deployment?