whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update content/en/docs/reference/labels-annotations-taints.md

Browse Source 
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Paco Xu
2021-03-19 13:14:30 +08:00
committed by pacoxu
parent c78dbec7ae
commit 352e776eed
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/labels-annotations-taints.md
+6 -6
View File
@@ -198,6 +198,12 @@ The kubelet can set this annotation on a Node to denote its configured IPv4 addr
When kubelet is started with the "external" cloud provider, it sets this annotation on the Node to denote an IP address set from the command line flag (`--node-ip`). This IP is verified with the cloud provider as valid by the cloud-controller-manager.
## kubectl.kubernetes.io/default-container
Example: `kubectl.kubernetes.io/default-container: "front-end-app"`
The value of the annotation is the container name that is default for this Pod. For example, `kubectl logs` or `kubectl exec` without `-c` or `--container` flag will use this default container.
**The taints listed below are always used on Nodes**
## node.kubernetes.io/not-ready
@@ -253,9 +259,3 @@ Sets this taint on a node to mark it as unusable, when kubelet is started with t
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.