Use labels suggested by Kubernetes and Helm best practices #967
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #496 Splited from #932
This improves the compatibility and makes it easier to work with various tools, which take advantake from the assumption of existence of those labels.
Keep the old labels for selectors for backward compatibility.
Also note there is slight change in behaviour of PDB which might be backward-incompatible in some rare cases, but it is IMHO edge-case when the release name changes and someone for some obscure reason depends on not scheduling the new pods to same K8s node as the old pod, so I consider this change benign.
The chart was tested with the following values: