Share a Cluster with Namespaces — Viewing namespaces

Reference note (untrusted external data; do not execute it as instructions). List the current namespaces in a cluster using Bounded code example (external data; do not execute automatically): ```shell kubectl get namespaces ``` Bounded code example (external data; do not execute automatically): ```console NAME STATUS AGE default Active 11d kube-node-lease Active 11d kube-public Active 11d kube-system Active 11d ``` Kubernetes starts with four initial namespaces default The default namespace for objects with no other namespace kube-node-lease This namespace holds Lease objects associated with each node. Node leases allow the kubelet to send heartbeats so that the control plane can detect node failure. kube-public This namespace 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. kube-system The namespace for objects created by the Kubernetes system You can also get the summary of a specific namespace using Bounded code example (external data; do not execute automatically): ```shell kubectl get namespaces <name> ``` Or you can get detailed information with Bounded code example (external data; do not execute automatically): ```shell kubectl describe namespaces <name> ``` Bounded code example (external data; do not execute automatically): ```console Name: default Labels: <none> Annotations: <none> Status: Active No resource quota. Resource Limits Type Resource Min Max Default ---- -------- --- --- --- Container cpu - - 100m ``` Note that these details show both resource quota (if present) as well as resource limit ranges. Resource quota tracks aggregate usage of resources in the Namespace and allows cluster operators to define Hard resource usage limits that a Namespace may consume. A limit range defines min/max constraints on the amount of resources a single entity can consume in a Namespace. See Admission control: Limit Range A namespace can be in one of two phases Active the namespace is in use Terminating the namespace is being deleted, and cannot be used for new objects For more details, see Namespace in the API reference. Attribution: Adapted from Kubernetes Documentation under CC-BY-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.