docs: refresh CLI examples and manifests for kOps 1.37

[rifelpet]

Every YAML example under docs/ was strict-decoded through the kOps API scheme, and every documented kops command was checked against the 1.37 flag set. That surfaced a number of examples that current kOps would reject outright.

Examples that would be rejected today

• networking.kubeRouter and calico.IPIPMode do not match the JSON tags in the API types — they are kuberouter and ipipMode.
• clusterAutoscaler.scaleDownUtilizationThreshold and a kubeAPIServer env value were unquoted numbers, but both fields are strings.
• An InstanceGroup in the Spot Ocean docs had its spec nested under metadata.
• iam_roles.md used the long-removed zones field instead of subnets.
• The GPU taint was shown as a Kubernetes taint object, but the kOps taints field takes strings; the value kOps actually sets is nvidia.com/gpu:NoSchedule.
• A missing line continuation split the GCE kops create cluster command.

Renamed flags

--master-zones, --master-size, --master-count, --master-volume-size and --master-interval moved to --control-plane-*, and --vpc is now --network-id. kops toolbox instance-selector takes the instance group name as a positional argument.

Removed features

Dropped the containerRuntime and spec.docker sections — validation now rejects containerRuntime: docker outright, and docker.service in the hooks example became containerd.service.

Stale versions and images

Kubernetes 1.36.4 (latest recommended in channels/stable), containerd 2.3.4, and Ubuntu 24.04 in place of focal, CoreOS, kope.io and debian-9 references. The exported manifest in manifests_and_customizing_via_api.md was regenerated with kops create cluster --dry-run -o yaml rather than hand-edited.

Worth a look during review

• images.md — I removed the "Ubuntu 20.04 (Focal)" and "Debian 10 (Buster)" sections. Both were removed in kOps 1.36 and were the only removed distros still listed under "Supported Distros". This leaves a dead fragment in an old release note (the page still resolves, just not the anchor). Happy to drop this hunk if you'd rather keep them.
• coreos-kops-tests-multimaster.md — only the flags were fixed. The doc is an end-to-end CoreOS tutorial and CoreOS was removed in kOps 1.18, so the AMI IDs and coreos.com URLs are all dead. It probably wants deleting or rewriting against a supported distro, which felt out of scope here.

Examples stay on the v1alpha2 apiVersion, which is what kOps writes today.

59 YAML blocks still do not strict-decode; each was checked by hand and they are intentional ... elisions, Go templates in cluster_template.md, non-kOps manifests, and shell transcripts.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UwhWXUuoWwsv9WSzGAkanj

[hakman]

/override pull-kops-e2e-k8s-aws-calico

[kubernetes-prow]

@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-k8s-aws-calico

Details

In response to this:

/override pull-kops-e2e-k8s-aws-calico

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hakman]

/lgtm
/approve

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment