kubeadm upgrade phase

    Using this phase you can choose to execute the separate steps of the upgrade of secondary control-plane or worker nodes. Please note that kubeadm upgrade apply still has to be called on a primary control-plane node.

    Use this command to invoke single phase of the node workflow

    Use this command to invoke single phase of the node workflow

    Options

    Options inherited from parent commands

    —rootfs string

    [EXPERIMENTAL] The path to the ‘real’ host root filesystem.

    Run upgrade node pre-flight checks

    Synopsis

    Run pre-flight checks for kubeadm upgrade node.

    Options inherited from parent commands

    —rootfs string

    [EXPERIMENTAL] The path to the ‘real’ host root filesystem.

    Upgrade the control plane instance deployed on this node, if any

    Synopsis

    Upgrade the control plane instance deployed on this node, if any

    Options

    —rootfs string

    [EXPERIMENTAL] The path to the ‘real’ host root filesystem.

    Upgrade the kubelet configuration for this node

    Synopsis

    Download the kubelet configuration from the kubelet-config ConfigMap stored in the cluster

    Options

    Options inherited from parent commands

    —rootfs string

    [EXPERIMENTAL] The path to the ‘real’ host root filesystem.

    What’s next

    • to bootstrap a Kubernetes control-plane node
    • kubeadm join to connect a node to the cluster
    • to revert any changes made to this host by or kubeadm join
    • kubeadm upgrade to upgrade a kubeadm node
    • to try experimental functionality