Git and kubectl: A Fast, Safe Deployment Workflow

The terminal waits for your command. One keystroke can push code, roll a cluster, and change production.

Git and kubectl are the two tools that govern that workflow. Git tracks your source code. Kubectl controls your Kubernetes clusters. Together, they make deployment fast, repeatable, and safe—when used with discipline.

Git gives you version control. Every commit is a record of what changed and why. You can switch branches, merge features, and roll back to a stable state in seconds. Good branching strategy keeps your main branch deployable at all times.

Kubectl lets you interact with Kubernetes from the command line. You query resources, inspect cluster health, and apply changes. It talks to the Kubernetes API and can create, update, scale, or delete workloads.

The real power comes when you connect Git and kubectl. Store your Kubernetes manifests in Git. Tag releases when your code is ready. Use CI/CD to apply those manifests with kubectl against staging or production. This creates GitOps: the cluster state matches what’s in your Git repo, and every change is traceable.

Essential commands:

• kubectl get pods shows what’s running now.
• kubectl describe drills into resource details.
• kubectl apply -f applies manifest files from Git to the cluster.
• kubectl rollout status watches the progress of new deployments.

When a change fails, revert the Git commit and re-apply with kubectl to restore stability. This workflow removes guesswork—always know what version runs in production and how to get back to a known good state.

Good security practice means limiting kubectl access, using role-based access control (RBAC), and requiring peer review before merging Git changes that affect Kubernetes manifests.

Git and kubectl form a complete control loop: define, commit, apply, verify. Fast feedback, consistent deployments, and stable systems follow.

See how this works in action with live Git-to-kubectl deployment pipelines at hoop.dev and get it running in minutes.