Kubernetes-native Orka resource management

Everything you need to tap into the underlying Kubernetes layer of Orka. Starting with Orka 3.0, all Orka resources are Kubernetes-native. They are custom resources with detailed custom resource definitions. This lets you work with Orka resources straight from kubectl, if that’s your preferred tool. You can also run custom pods in namespaces, created with the enable custom pods setting.

The recommended way to work with Orka resources is via the Orka CLI, Orka API, or the Orka Web UI. You can still use kubectl instead, but exercise caution and consider managing only VMs and VM configs via YAML. Working with images, ISOs, or nodes directly requires both advanced Orka CRD and Kubernetes knowledge, and might result in unexpected issues.

Workflow

Install kubectl locally or upgrade your existing installation. For example:

brew install kubectl

# OR

brew upgrade kubectl

Authenticate with your Orka cluster:

Orka CLI

orka login

# OR

orka user set-token

Manage Orka resources with kubectl:

kubectl apply -f <FILE_NAME> --namespace=<NAMESPACE>

# OR

kubectl get <RESOURCE> --namespace=<NAMESPACE>

# OR

kubectl edit <RESOURCE> --namespace=<NAMESPACE>

# OR

kubectl delete <RESOURCE> --namespace=<NAMESPACE>

Create and configure a namespace for running custom pods.

First, you need to create a namespace with enabled custom pods. Next, you must grant access to the namespace to the users who need to deploy to it. And finally, you need to assign computational resources to the namespace. Note that you will not be able to deploy Orka resources to this namespace. Orka CLI

orka namespace create <NAMESPACE_NAME> --enable-custom-pods

orka rb add-subject --user <EMAIL_ADDRESS> --namespace <NAMESPACE_NAME>

orka node namespace <NODE_NAME> <NAMESPACE_NAME>

Manage your custom pods with kubectl.

kubectl apply -f <FILE_NAME> --namespace=<NAMESPACE_NAME>

# OR

kubectl get <CUSTOM_POD> --namespace=<NAMESPACE_NAME>

# OR

kubectl edit <CUSTOM_POD> --namespace=<NAMESPACE_NAME>

# OR

kubectl delete <CUSTOM_POD> --namespace=<NAMESPACE_NAME>

For any custom pods you need to run, add the following toleration to the pod: YAML

{"key": "orka.macstadium.com/namespace-reserved", "value": "<NAMESPACE_NAME>"}

Limitations

Your access to Orka resources depends on the role of the user you authenticated with. For more information, see here.
You can run custom pods only in a namespace created with the enable custom pods setting.
You cannot run custom pods in the orka-default namespace.
For any custom pods you want to run, you must add the following toleration:

YAML

{"key": "orka.macstadium.com/namespace-reserved", "value": "<NAMESPACE_NAME>"}

MacStadium

Orka

MacStadium VDI

IaaS

Kubernetes-native Orka resource management

Workflow

Limitations

​Workflow

​Limitations

Workflow

Limitations