Common kubectl commands every developer should know
There are hundreds of kubectl subcommands and you will use about fifteen. This is that fifteen,
with the flags that turn each one from "prints something" into "answers the question."
Workloads, controllers, and the API that ties them together.
View All TagsThere are hundreds of kubectl subcommands and you will use about fifteen. This is that fifteen,
with the flags that turn each one from "prints something" into "answers the question."
kind — Kubernetes IN Docker — runs each Kubernetes node as a Docker container. That sounds like a toy, but the nodes run real kubelets, a real control plane, and real container runtimes, which makes it the closest you can get to a production topology on a laptop. It is also what the Kubernetes project itself uses for conformance testing.
Every command below has been written to run as-is.
Kubernetes networking has a reputation for being impenetrable. It mostly is not — there are about five ideas, and the confusion comes from the fact that ClusterIPs are virtual addresses that no machine actually owns. Once that clicks, the rest follows.
Newcomers to Kubernetes almost always ask the same question in the same order: what is a Pod, why would I not just create one, and what does a Deployment add? The answer is a three-level chain of ownership, and once you can see it, most of Kubernetes' behaviour stops being surprising.