Admin only: All namespace operations require administrative privileges.
Understanding namespaces
Namespaces are used for grouping and dedicating resources to specific Orka users or service accounts. All users have access to the orka-default namespace. Based on specific rolebindings, a user or a service account might also be able to access the resources within additional namespaces.
Key concepts:
- Resource isolation: VMs, nodes, and resources in one namespace are separate from other namespaces
- Access control: Users and service accounts must be granted access to namespaces via rolebindings
- Default namespace: All users have access to
orka-default by default
- Custom pods: Some namespaces can be configured to run custom Kubernetes resources instead of Orka VMs
All cluster namespaces must have the orka- prefix.
Creating namespaces
orka3 namespace create
Create a new namespace with the specified name.
Namespace name requirements:
- Begins with the
orka- prefix
- Does not exceed 63 characters (including the prefix)
- Consists of lowercase alphanumeric characters or dashes (-)
- Ends with an alphanumeric character
- Must be unique to the cluster
If --enable-custom-pods is set, creates a new namespace dedicated to running custom K8s resources (formerly sandboxing). Orka VMs cannot be deployed in that namespace.
After creating a namespace:
- Move one or more nodes to the namespace to provide computational resources:
- Provide explicit access to users or service accounts:
Syntax:
Options:
Examples:
Listing namespaces
orka3 namespace list
List all namespaces for the Orka cluster. Use this command to check if one or more specific namespaces already exist.
Syntax:
Options:
Examples:
Deleting namespaces
orka3 namespace delete
Delete the specified namespace. All VMs (or custom pods) must be removed and nodes must be moved out of the namespace before running this operation.
This is a destructive operation and cannot be undone. To restore a deleted namespace, re-create it, move the respective Orka nodes, and re-add the respective users to the respective role bindings.
Syntax:
Options:
Examples: