Editing Kubernetes namespaces
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 3: | Line 3: | ||
* <code>[[kube-system]]</code> for objects created by the Kubernetes system. | * <code>[[kube-system]]</code> for objects created by the Kubernetes system. | ||
* <code>[[kube-public]]</code> is created automatically and is readable by all users (including those not authenticated). This namespace is mostly reserved for cluster usage, in case that some resources should be visible and readable publicly throughout the whole cluster. The public aspect of this namespace is only a convention, not a requirement. | * <code>[[kube-public]]</code> is created automatically and is readable by all users (including those not authenticated). This namespace is mostly reserved for cluster usage, in case that some resources should be visible and readable publicly throughout the whole cluster. The public aspect of this namespace is only a convention, not a requirement. | ||
− | * <code>[[kube-node-lease]]</code> holds [[ | + | * <code>[[kube-node-lease]]</code> holds [[Lease objects]] associated with each node. Node leases allow the <code>[[kubelet]]</code> to send [[heartbeats]] so that the control plane can detect node failure. |
Additional documentation: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ | Additional documentation: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ |
Advertising: