Kubernetes on macOS: Getting started

Kubernetes is incredibly powerful — and equally intimidating when you’re starting out.
When I first explored Kubernetes, I struggled to find a simple, structured path to getting it running on my development machine.
This guide is what I wish I had back then.

Prerequisite: You should already be comfortable with Docker and understand its basic concepts.

Installing Kubernetes Locally

There are many tools for running Kubernetes locally — minikube, k3s, k0s, k3d, etc.
For macOS, I recommend Orbstack, which offers native Kubernetes support.

Why Orbstack?
Orbstack automatically configures service DNS (<service>.<namespace>.svc.cluster.local), so you don’t have to mess with /etc/hosts manually. This makes testing, debugging, and development much easier.

After installing Orbstack, start Kubernetes:

1
$ orb start k8s

If orb isn’t found, double-check your Orbstack installation.

Verify Kubernetes is running:

1
$ kubectl config get-contexts
2
CURRENT   NAME       CLUSTER    AUTHINFO   NAMESPACE
3
*         orbstack   orbstack   orbstack

Your First Deployment

If you’ve used Podman, you’re already familiar with Pods.
In Kubernetes, Pods usually sit behind a higher-level abstraction: Deployments.

In Docker, you launch a container like this:

1
$ docker run nginx

In Kubernetes, you describe containers in YAML and apply the configuration with kubectl.

Create a file example.yaml:

1
apiVersion: apps/v1
2
kind: Deployment
3
metadata:
4
  name: example-deployment # deployment name
5
spec:
6
  selector:
7
    matchLabels:
8
      app: example-pod # -----
9
  template: #    |
10
    metadata: #    |
11
      labels: #    |
12
        app: example-pod # <--
13
    spec:
14
      containers:
15
        - name: example-container
16
          image: nginx
17
          imagePullPolicy: Always
18
          ports:
19
            - containerPort: 80
20
---
21
apiVersion: v1
22
kind: Service
23
metadata:
24
  name: example-service
25
spec:
26
  selector:
27
    app: example-pod # selector which pod
28
  ports:
29
    - protocol: TCP
30
      port: 8080 # exposed port
31
      targetPort: 80 # container port

Apply the configuration:

1
$ kubectl apply -f example.yaml
2
deployment.apps/example created
3
service/example-service created

Check the deployment status:

1
$ kubectl get deployments --watch
2
NAME      READY   UP-TO-DATE   AVAILABLE   AGE
3
example   1/1     1            1

Wait until READY shows 1/1.

Check the running pods:

1
$ kubectl get pods --watch
2
NAME                       READY   STATUS    RESTARTS   AGE
3
example-54c9b4c747-v7mbj   1/1     Running   0          10s

Accessing Your Application

Your service is now reachable at:

http://example-service.default.svc.cluster.local:8080/

You can also access it via its cluster IP:

1
$ kubectl get svc
2
NAME              TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)    AGE
3
example-service   ClusterIP   192.168.194.207   <none>        8080/TCP   2s

Note: Cluster IPs change after restarting services. DNS access via Orbstack remains stable.

Cleaning Up

Delete your resources:

1
$ kubectl delete -f example.yaml

Verify pods are gone:

1
$ kubectl get pods
2
No resources found in default namespace.

Understanding Kubernetes Layers

Level 1: Docker — Direct Container

1
docker run nginx  →  [ Container ]

• Single container, immediate run.

Level 2: Podman — Pod-Based Grouping

1
$ podman pod create --name mypod             →  [ Pod ]
2
$ podman run --pod mypod -p 8080:80 nginx    →     ├─ [ Container ]
3
$ podman run --pod mypod redis               →     └─ [ Container ]

• Multiple containers share a network namespace.

Level 3: Kubernetes — Declarative Deployment

1
YAML (Deployment) → kubectl apply → [ Deployment ]
2
                                        └─ [ Pod ]
3
                                             ├─ [ Container ]
4
                                             └─ [ Container ]

• Declarative infrastructure, automated scaling and healing.

What Is a Deployment?

A Deployment in Kubernetes manages Pods, ensuring the desired number of replicas are always running.

You can scale your deployment by adding replicas: 2 to your example.yaml:

1
---
2
spec:
3
  replicas: 2

Apply changes:

1
$ kubectl apply -f example.yaml

List your pods:

1
$ kubectl get pods
2
NAME                                  READY   STATUS    RESTARTS   AGE
3
example-deployment-779f6bb7dc-nvvq7   1/1     Running   0          4s
4
example-deployment-779f6bb7dc-wlfzg   1/1     Running   0          4s

Kubernetes will automatically distribute traffic between the two instances.

Read more about deployments.

What Is a Service?

A Service in Kubernetes provides a stable way to access one or more Pods.
It assigns a Cluster IP (internal virtual IP) and a DNS name (e.g., example-service.default.svc.cluster.local) inside the cluster.

However, it’s important to understand the difference between running Kubernetes in k3d (or any other tool) versus Orbstack:

k3d

• k3d runs Kubernetes inside a Docker container.
• The internal DNS names (*.svc.cluster.local) are only resolvable inside the cluster (between Pods).
• Your host machine (macOS) is not part of the cluster’s network.
• As a result, you cannot reach example-service.default.svc.cluster.local directly from your Mac without special DNS routing or port-forwarding.
• Typical workarounds:
  • kubectl port-forward
  • Exposing services as NodePort
  • Setting up an Ingress controller

Orbstack

• Orbstack tightly integrates your host machine into the cluster network.
• It automatically configures DNS so that .svc.cluster.local names are resolvable from your Mac.
• You can directly open http://example-service.default.svc.cluster.local:8080/ in your browser without any extra configuration.
• This makes development, debugging, and service access much simpler.

Orbstack gives you a much smoother local development experience by bridging the cluster and host DNS automatically, while k3d needs extra setup if you want to access services easily from your Mac.

Read more about services.

Conclusion

Setting up Kubernetes on macOS doesn’t have to be painful.

With Orbstack, a few YAML files, and some kubectl commands, you can be up and running fast — and focus on learning Kubernetes without unnecessary friction.

What’s Next?

Now that you have Kubernetes running locally and deployed your first app, here are some great next steps to deepen your knowledge:

• Explore kubectl Commands
  Learn how to inspect Pods, Services, Deployments, and troubleshoot issues using kubectl describe, kubectl logs, and kubectl exec.

• Dive Into Helm
  Helm is the package manager for Kubernetes. It helps you install complex applications easily.
  Recommended starting point: Helm Quickstart Guide

• Understand Ingress Controllers
  Move beyond ClusterIP and NodePort services by setting up an Ingress (like Traefik or NGINX) to manage external access to your apps.

• Learn about StatefulSets, Jobs, and CronJobs
  Deploy workloads that require persistent storage or scheduled execution — not everything fits neatly into stateless Deployments.

• Set Up Local CI/CD Pipelines
  Try integrating your Kubernetes setup with local GitOps tools like ArgoCD or simple CI pipelines that deploy automatically into your cluster.

• Join the Community
  Engage with Kubernetes communities (Slack, Discord, CNCF meetups) to stay updated and ask questions when stuck.

Kubernetes has a steep learning curve — but with a solid local setup and consistent hands-on practice, you’ll progress faster than you think.

Happy clustering!