Difference between revisions of "Kubernetes namespaces"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
Tags: Mobile web edit, Mobile edit |
|||
| Line 1: | Line 1: | ||
Kubernetes starts with four initial namespaces: <ref>https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/</ref> | Kubernetes starts with four initial namespaces: <ref>https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/</ref> | ||
| − | * <code>default</code> is the default namespace for objects with no other namespace. | + | * <code>[[default]]</code> is the default namespace for objects with no other namespace. |
* <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. | ||
Revision as of 11:37, 4 October 2023
Kubernetes starts with four initial namespaces: [1]
defaultis the default namespace for objects with no other namespace.kube-systemfor objects created by the Kubernetes system.kube-publicis 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-leaseholds lease objects associated with each node. Node leases allow thekubeletto 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
Contents
Commands
kubectl get namespaceskubectl create namespace MY_TEST_NAMESPACEkubectl create namespace argocdkubectl describe namespacekubectl get all --all-namespaceskubectl get pods --all-namespaceskubectl label namespace
Activities
Related terms
kind: namespacehelm listhelm install -n, --namespaceNo resources found in default namespace.kubectl get configmaps -Adefault, kube-node-lease, kube-public, kube-system- Namespace controller
kubens
EKS namespaces:
See also
kubectl: [cp | config | create|delete|edit | explain |apply|exec|get|set|drain | uncordon | rolling-update|rollout|logs|run|auth|label | annotate|version|top|diff|debug|replace|describe|port-forward | proxy|scale|rollout|api-resources| expose deployment | expose | patch | attach | get endpoints | ~/.kube/config | kubectl logs --help | kubectl --help, kubectl-convert, kubectl autoscale, kubectl.kubernetes.io- Kubernetes namespaces:
kubectl get namespaces,kube-system namespace,--namespace
Advertising:
