Tomek Święcicki 5776fdbe02 [bitnami/haproxy] Update apiVersion of PDB to policy/v1 on 1.21+ cluster (via common.capabilities.policy.apiVersion) (#7368) ...

* Update apiVersion of PDB to policy/v1

According to https://kubernetes.io/docs/reference/using-api/deprecation-guide/ we can start using `policy/v1` in Kubernetes `1.21.

Without that you can observe such things in logs:

```
client.go:209: [debug] checking 5 resources for changes
W0901 11:28:35.264440      91 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
W0901 11:28:35.269403      91 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
W0901 11:28:35.297605      91 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
```

* use common.capabilities.policy.apiVersion

* bump chart version to 0.2.8

2021-09-06 10:03:25 +02:00

..

_helpers.tpl

…

configmap.yaml

…

deployment.yaml

[bitnami/haproxy] Add Configmap checksum annotation (#7174)

2021-08-10 19:45:05 +02:00

extra-list.yaml

…

hpa.yaml

…

NOTES.txt

…

pdb.yaml

[bitnami/haproxy] Update apiVersion of PDB to policy/v1 on 1.21+ cluster (via common.capabilities.policy.apiVersion) (#7368)

2021-09-06 10:03:25 +02:00

service-account.yaml

[bitnami/haproxy] Adding condition to serviceaccount (#7177)

2021-08-12 17:53:21 +02:00

service.yaml

…