Deploy Kubernetes Without a Repo – Step-by-Step Guide

Introduction

Deploying applications to Kubernetes (K8s) typically involves pushing container images to a public or private repository like Docker Hub or AWS ECR. However, there are scenarios where you might want to deploy directly from a local machine without using a repository. This guide covers various methods to deploy Kubernetes applications without needing a repository, making the process efficient and flexible.

Why Deploy to Kubernetes Without a Repository?

Common Use Cases

• Local Development: Deploy applications quickly for testing without publishing images.

• Air-Gapped Environments: Secure environments where external access is restricted.

• Avoiding Image Registry Costs: Save costs associated with hosting container images.

• Rapid Prototyping: Quickly test and iterate without registry dependencies.

Methods to Deploy Kubernetes Without a Repo

1. Using Minikube Image Load (For Local Clusters)

Minikube allows you to load local Docker images into its internal Docker registry.

Steps:

1. Build your Docker image locally:

   docker build -t my-app:latest .

2. Load the image into Minikube:

   minikube image load my-app:latest

3. Deploy to Kubernetes:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: my-app
   spec:
     replicas: 1
     selector:
       matchLabels:
         app: my-app
     template:
       metadata:
         labels:
           app: my-app
       spec:
         containers:
         - name: my-app
           image: my-app:latest
           ports:
           - containerPort: 80

4. Apply deployment:

   kubectl apply -f deployment.yaml

2. Using KIND (Kubernetes in Docker)

KIND enables Kubernetes clusters to run inside Docker containers. It supports loading images directly.

Steps:

1. Build the image:

   docker build -t my-app:latest .

2. Load it into KIND:

   kind load docker-image my-app:latest

3. Deploy using the same YAML configuration as above.

3. Using a Private Docker Registry

Setting up a private registry allows you to avoid using public repositories while still enabling deployment.

Steps:

1. Run a local registry:

   docker run -d -p 5000:5000 --name registry registry:2

2. Tag and push the image:

   docker tag my-app:latest localhost:5000/my-app:latest
   docker push localhost:5000/my-app:latest

3. Update the deployment YAML to use localhost:5000/my-app:latest

Troubleshooting Common Issues

1. ImagePullBackOff Error

• Ensure the image is loaded into the cluster.

• Use kubectl describe pod <pod-name> to check detailed error messages.

2. Node Not Running

• Run kubectl get nodes and kubectl describe node <node-name> to check the status.

3. Service Not Accessible

• Expose it via NodePort:

  kubectl expose deployment my-app --type=NodePort --port=80

• Use minikube service my-app --url to access.

FAQ

1. Can I deploy to a cloud Kubernetes cluster without a repo?

Yes, but you need to transfer images to cluster nodes manually or use a private registry.

2. How do I deploy an image to a remote Kubernetes cluster without a registry?

• Save the image as a tar file:

  docker save my-app:latest -o my-app.tar

• Copy it to the cluster node:

  scp my-app.tar user@remote-node:/tmp

• Load the image:

  ssh user@remote-node "docker load -i /tmp/my-app.tar"

3. How can I verify if my image is available in the cluster?

Run:

kubectl get pods -o wide

Check if the correct image is used.

External Resources

• Kubernetes Official Documentation

• Minikube Image Loading

• Kubernetes KIND Documentation

Conclusion

Deploying applications to Kubernetes without a repository is useful for local development, air-gapped environments, and cost savings. Using Minikube, KIND, or a private registry enables flexible deployment workflows. By following this step-by-step guide, you can efficiently deploy Kubernetes applications without relying on external repositories. Thank you for reading the huuphan.com page!