Updates and Upgrades

    From Github:

    You can also rerun these steps if previously built from source.

    Linux

    You can also rerun these steps if previously built from source.

    You may want to run below commands to include fixes/features after updating kOps

    Upgrading Kubernetes

    The kops upgrade command also automates checking for and applying updates.

    It is recommended to run the latest version of kOps to ensure compatibility with the target kubernetesVersion. When applying a Kubernetes minor version upgrade (e.g. v1.5.3 to v1.6.0), you should confirm that the target kubernetesVersion is compatible with the current kOps release.

    • kops edit cluster $NAME
    • set the kubernetesVersion to the target version (e.g. v1.3.5) Note the verb used below is update, not upgrade.
    • kops update cluster $NAME to preview, then
    • kops rolling-update cluster $NAME to preview, then kops rolling-update cluster $NAME --yes

    Automated update

    • kops upgrade cluster $NAME to preview, then kops upgrade cluster $NAME --yes
    • kops update cluster $NAME to preview, then kops update cluster $NAME --yes
    • kops rolling-update cluster $NAME to preview, then kops rolling-update cluster $NAME --yes

    Upgrade uses the latest Kubernetes version considered stable by kOps, defined in https://github.com/kubernetes/kops/blob/master/channels/stable.

    • set the kubernetesVersion to the target version (e.g. v1.3.5)
    • NOTE: The next 3 steps must all be run in the same directory. Here, --out=. specifies that the Terraform files will be written to the current directory. It should point to wherever your Terraform files from kops create cluster exist. The default is out/terraform.
    • kops update cluster $NAME --target=terraform --out=.
    • terraform plan
    • terraform apply
    • kops rolling-update cluster $NAME to preview, then kops rolling-update cluster $NAME --yes

    Other Notes:

    • In general, we recommend that you upgrade your cluster one minor release at a time (1.17 —> 1.18 —> 1.19). Although jumping minor versions may work if you have not enabled alpha features, you run a greater risk of running into problems due to version deprecation.