feat: add support for default container annotation (#8015) #9769
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.
By using the (
kubectl.kubernetes.io/default-container
annotation)[https://kubernetes.io/docs/reference/labels-annotations-taints/#kubectl-kubernetes-io-default-container] on a pod, we can let developers decide default, both for argocd and kubectl.It's particularly useful if/when sidecars decide where to be injected, as mentioned in the issue linkerd recently changed to be the first starting container (linkerd/linkerd2#5967) causing UI to always open up logs on that tab.
Fixes #8015
Checklist: