From c78dbec7ae5c62bcb2dcc41845af1e36b1314795 Mon Sep 17 00:00:00 2001 From: pacoxu Date: Wed, 17 Mar 2021 16:00:06 +0800 Subject: [PATCH] add kubectl.kubernetes.io/default-container to well known annotations --- content/en/docs/reference/labels-annotations-taints.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/en/docs/reference/labels-annotations-taints.md b/content/en/docs/reference/labels-annotations-taints.md index 8f4327ceca..3d62069d40 100644 --- a/content/en/docs/reference/labels-annotations-taints.md +++ b/content/en/docs/reference/labels-annotations-taints.md @@ -254,3 +254,8 @@ Example: `node.cloudprovider.kubernetes.io/shutdown:NoSchedule` If a Node is in a cloud provider specified shutdown state, the Node gets tainted accordingly with `node.cloudprovider.kubernetes.io/shutdown` and the taint effect of `NoSchedule`. +## kubectl.kubernetes.io/default-container + +Example: `kubectl.kubernetes.io/default-container:container1` + +If a Pod has the annotation `kubectl.kubernetes.io/default-container`, consumers (CLI, operators) know which is the default container. For example, `kubectl logs` or `kubectl exec` without `-c` or `--container` flag will use this default container.