Namespace provides a scope for Names. Use of multiple namespaces is optional.

APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

NamespaceSpec describes the attributes on a Namespace.

Finalizers is an opaque list of values that must be empty to permanently remove object from storage. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/

Spec defines the behavior of the Namespace. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

NamespaceStatus is information about the current status of a Namespace.

NamespaceCondition contains details about state of namespace.

Represents the latest available observations of a namespace's current state.

Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/

Status describes the current status of a Namespace. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

You won't find a simpler example than this one.

Create a namespace named 'my-namespace'

1. Create a namespace named 'my-namespace'

It's a good practice to add labels and annotations to your namespaces to help you organize resources in your cluster.

v1 · Cluster Resource

Namespace

Looking for some examples?

Other useful resources