added PodDisruptionBudget in kustomize & helm

[haarchri]

Signed-off-by: Christopher Haar chhaar30@googlemail.com

What type of PR is this

/kind feature PodDisruptionBudget

Proposed Changes

added PodDisruptionBudget in kustomize & helm

Proof Manifests

apiVersion: policy/v1beta1
kind: PodDisruptionBudget
metadata:
  labels:
    app: kyverno
    app.kubernetes.io/component: kyverno
    app.kubernetes.io/instance: kyverno
    app.kubernetes.io/managed-by: Kustomize
    app.kubernetes.io/name: kyverno
    app.kubernetes.io/part-of: kyverno
    app.kubernetes.io/version: v1.3.6
  name: kyverno
  namespace: kyverno
spec:
  minAvailable: 1
  selector:
    matchLabels:
      app: kyverno
      app.kubernetes.io/name: kyverno

Checklist

• I have read the contributing guidelines.
• I have read the PR documentation guide and followed the process including adding proof manifests to this PR.

[realshuting]

@haarchri - thanks for the contribution, it looks good to me!

@JimBugwadia @chipzoller - can you please take a look?

[JimBugwadia]

I am not very clear on the current best practices for PDB, but should the default settings for a single replica contain:

minAvailable: 1

Will this potentially prevent nodes from being drained as discussed here jupyterhub/zero-to-jupyterhub-k8s#1934?

[haarchri]

@JimBugwadia i changed the default for kustomize to

minAvailable: 0

for helm chart the default is disabled - and the other configuration is done in values.yaml

[realshuting]

@JimBugwadia - is there any change needed at this point? Should we merge the PR?

[haarchri]

did you need something for this PR to merge ?

[realshuting]

Ping @JimBugwadia.

[JimBugwadia]

@ojhaarjun1 - No. Apologies for the delay. We will get this merged soon.

[realshuting]

Rebased and merged via #2463.