Kubernetes has a built-in manual. Most people never open it. It's the command kubectl explain, and kubectl is the Kubernetes command-line tool.

You're editing a Deployment and need the fields under strategy. So you open five tabs of docs and forum answers, and you're still unsure which match your version. On the other side, one terminal command, kubectl explain deployment.spec.strategy, reads the answer from your running cluster.

Here's the command, and here's what comes back. First, a description of strategy, how Deployments replace old pods with new ones. Then its child fields, type and rollingUpdate. This comes from your cluster's own schema, so it matches your running version. Layout can vary slightly between kubectl versions.

A dotted path is just resource, field, subfield, the same nesting you write in YAML. Add .rollingUpdate to the path and you land on maxSurge and maxUnavailable. Want the whole tree at once? Add --recursive. And this works the same way for any resource.

Your cluster already publishes its own field documentation. Next time you're unsure about a field, run kubectl explain before opening a tab. Stop searching. Ask your cluster.