* 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
* Adding condition to serviceaccount
* fixed redis typo
* removed unrelated changed keeping condition only
Bump chart version number
* Adding new line
bumping chart version number
* Rebase master
* Fix typo in statefulset
* Include lifecycle in the if statement
* Include metrics container
* Update README
* Rebase master
* Rebase master
* Rebase master
* Add diagnostic mode to etcd
* Add diagnostic mode to fluentd
* Add diagnostic mode to grafana-tempo
* Add diagnostic mode to haproxy
* Rebase master
* Fix values location and README
* Add diagnostic mode to the scaffolding
* Add diagnostic mode to kafka
* Add diagnostic mode to kong
* Fix linter in ejbca
* Add diagnostic mode to logstash
* Add diagnostic mode to mariadb
* Add diagnostic mode to mongodb-sharded
* Fix BITNAMI_DEBUG in galera
* Add diagnostic mode to mysql
* Add diagnostic mode to nats
* Add diagnostic mode to postgresql
* Add diagnostic mode to rabbitmq
* Add diagnostic mode to redis-cluster
* Add diagnostic mode to spark
* Add diagnostic mode to wordpress
* Add diagnostic mode to zookeeper
* Fix/Add BITNAMI_DEBUG in kong, nats, and spark
* Update READMEs
* Unify 'Please be patient...' sentence in NOTES
* Bump galera version