Kubernetes & Docker FAQs

📘

Orka 2.4.x content

This page has not been updated to reflect the changes introduced in Orka 3.0. Some of the information might be outdated or incorrect. Use 2.4.x to 3.0.0: API Mapping and 2.4.x to 3.0.0: CLI Mapping to figure out the correct endpoints and commands.

How do I access the underlying Kubernetes for my Orka environment?

After you set up a Kubernetes service account, you can manage any node with kubectl, Helm, and Tiller. For more information, see Kubernetes Sandbox.

👍

TIP: Isolate the node

If you want to perform only Kubernetes deployment management on a specific node, you can sandbox it with orka node sandbox. This disables deployment management with the Orka CLI.

What is sandboxing?

Sandboxing is a way to tell your cluster not to use a specific physical node. You can still deploy containers to it manually but Orka will not opt to use it when it has the choice. Sandboxing is a label that you can take on or off at any time.

For more information, see Kubernetes Sandbox.

How can I regenerate my .kubeconfig-orka file?

If your .kubeconfig-orka file is missing or corrupted, or you need to update the information in the file, you can regenerate it. Use the orka kube regenerate command.

The command deletes any existing .kubeconfig-orka files and creates a new one with the account information.

Can I manage my Orka environment entirely with kubectl?

You can use kubectl to manage some aspects of your Orka environment. Currently, kubectl commands are RBAC-limited to namespaces. For deployments, you need to use the Orka CLI, the Orka API, or the Orka web UI.

Where is the Kubernetes control plane running?

The control plane is running on the nodes. Orka uses a mesh cluster deployment. The nodes are the mesh, they are all master and they are all capable of failover.

Can I deploy a macOS VM with a .yml?

No. You need to use the Orka CLI, the Orka API, or the Orka web UI.

Orka is a customized namespace where you can't control deployments with kubectl and *.yml files. For your deployments, Orka creates a specialized pod descriptor and deploys it.

Can I use Kubernetes ingress and affinity rules?

Yes.

Are Orka VMs true Docker containers?

Orka uses Docker, but Orka macOS VMs are not traditional Docker containers. The instruction set for the macOS Docker containers are much more detailed than a normal Docker container.

The Docker container is a shell that wraps around the macOS VM so that it can be orchestrated with Kubernetes, as any other Docker container can be.

Functionally, each Orka VM is something between a Docker image and a full weight VM. The Orka macOS images are not traditional Docker images - they are full macOS VMs inside of a Docker "wrapper". The lightweight nature comes from Orka's take on storage and differentials. When you deploy a VM, Orka pulls a differential of the base image into a Docker container that looks, acts, and feels like a lightweight Docker container. In reality, it's similar to a link clone VM or an instant clone VM, that has been containerized and then orchestrated with Kubernetes.

Can I use the built-in VNC and Screen Sharing capabilities to connect to a pod?

No. The built-in VNC and Screen Sharing capabilities are available only for Orka macOS VMs.