Black lives matter.
We stand in solidarity with the Black community.
Racism is unacceptable.
It conflicts with the core values of the Kubernetes project and our community does not tolerate it.
Synopsis
Show what differences would be applied to existing static pod manifests. See also: kubeadm upgrade apply --dry-run
kubeadm upgrade diff [version] [flags]
Options
| --api-server-manifest string Default: "/etc/kubernetes/manifests/kube-apiserver.yaml" | |
| path to API server manifest | |
| --config string | |
| Path to a kubeadm configuration file. | |
| -c, --context-lines int Default: 3 | |
| How many lines of context in the diff | |
| --controller-manager-manifest string Default: "/etc/kubernetes/manifests/kube-controller-manager.yaml" | |
| path to controller manifest | |
| -h, --help | |
| help for diff | |
| --kubeconfig string Default: "/etc/kubernetes/admin.conf" | |
| The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. | |
| --scheduler-manifest string Default: "/etc/kubernetes/manifests/kube-scheduler.yaml" | |
| path to scheduler manifest | |
Options inherited from parent commands
| --rootfs string | |
| [EXPERIMENTAL] The path to the 'real' host root filesystem. | |