Difference between revisions of "Kubernetes namespaces"

From wikieduonline
Jump to navigation Jump to search
Line 29: Line 29:
 
* <code>[[kubens]]</code>
 
* <code>[[kubens]]</code>
  
EKS
+
EKS namespaces:
 
* <code>[[logging]]</code>
 
* <code>[[logging]]</code>
 
* <code>[[aws-load-balancer-controller]]</code> [[Ingress controller]]
 
* <code>[[aws-load-balancer-controller]]</code> [[Ingress controller]]

Revision as of 17:34, 12 December 2022

Kubernetes starts with four initial namespaces: [1]

  • default is the default namespace for objects with no other namespace.
  • kube-system for objects created by the Kubernetes system.
  • kube-public 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-node-lease holds lease objects associated with each node. Node leases allow the kubelet to send heartbeats so that the control plane can detect node failure.

Additional documentation: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ Other typical namespaces: monitoring, cluster-autoscaler

Commands

Activities

Related terms

EKS namespaces:

See also

  • https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
  • Advertising: