KUBERNETES(1)(kubernetes)

πŸ“¦
version 1.37.2 Β· 5 versions
, in arch rolling, fedora 43, fedora 44, nixpkgs unstable

πŸ’– KUBERNETES(1)(kubernetes) πŸ’–

okay bestie, so this is the kubeadm upgrade apply manual page β€” it lives in the kubernetes manual, and yes the legend Eric Paris was here in Jan 2015, we'll get to that at the end 🫢


✨ NAME ✨

kubeadm upgrade apply β€” Upgrade your Kubernetes cluster to the specified version πŸ‘‘


🌸 SYNOPSIS 🌸

kubeadm upgrade apply [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

Upgrade your Kubernetes cluster to the specified version. literally what it says on the tin, bestie, and it slays πŸ’…

The apply [version] command executes the following phases:

  • preflight β€” Run preflight checks before upgrade
  • control-plane β€” Upgrade the control plane
  • upload-config β€” Upload the kubeadm and kubelet configurations to ConfigMaps
    • upload-config/kubeadm β€” Upload the kubeadm ClusterConfiguration to a ConfigMap
    • upload-config/kubelet β€” Upload the kubelet configuration to a ConfigMap
  • kubelet-config β€” Upgrade the kubelet configuration for this node
  • bootstrap-token β€” Configures bootstrap token and cluster-info RBAC rules
  • addon β€” Upgrade the default kubeadm addons
    • addon/coredns β€” Upgrade the CoreDNS addon
    • addon/kube-proxy β€” Upgrade the kube-proxy addon
  • post-upgrade β€” Run post upgrade tasks

πŸŽ€ OPTIONS πŸŽ€

  • --allow-experimental-upgrades=false β€” Show unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes. (aka: let me live dangerously ✨)
  • --allow-release-candidate-upgrades=false β€” Show release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes.
  • --certificate-renewal=true β€” Perform the renewal of certificates used by component changed during upgrades.
  • --config="" β€” Path to a kubeadm configuration file.
  • --dry-run=false β€” Do not change any state, just output what actions would be performed. (the "look but don't touch" of it all πŸ™ˆ)
  • --etcd-upgrade=true β€” Perform the upgrade of etcd.
  • -f, --force=false β€” Force upgrading although some requirements might not be met. This also implies non-interactive mode. (no vibe check, just send it)
  • --ignore-preflight-errors=[] β€” A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
  • --kubeconfig="/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.
  • --patches="" β€” Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment", "kubeproxydaemonset". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically. (naming conventions stay EXACTLY as written, no editing the girlies πŸ’œ)
  • --print-config=false β€” Specifies whether the configuration file that will be used in the upgrade should be printed or not.
  • --skip-phases=[] β€” List of phases to be skipped
  • -y, --yes=false β€” Perform the upgrade and do not prompt for confirmation (non-interactive mode).

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • --rootfs="" β€” The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version

πŸ‘‘ SEE ALSO πŸ‘‘


πŸ“œ HISTORY πŸ“œ

January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since! (fr fr, the OG wrote this by hand and then everyone just... let the robots take over 😭 iconic either way)


and that's the whole thing, bestie β€” manual Manuals, section User, page KUBERNETES(1)(kubernetes). go upgrade that cluster. slay. periodt πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from