ContextQMD
Back to Kops

Updates and Upgrades

docs/operations/updates_and_upgrades.md

1.35.03.6 KB
Original Source

Updates and Upgrades

Updating kOps

MacOS

From Homebrew:

bash
brew update && brew upgrade kops

From Github:

bash
sudo rm -rf /usr/local/bin/kops
wget -O kops https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-darwin-amd64
chmod +x ./kops
sudo mv ./kops /usr/local/bin/

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

Linux

From Github:

bash
sudo rm -rf /usr/local/bin/kops
wget -O kops https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-linux-amd64
chmod +x ./kops
sudo mv ./kops /usr/local/bin/

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

kops update cluster $NAME --yes
kops rolling-update cluster $NAME --yes

Upgrading Kubernetes

Upgrading Kubernetes is easy with kOps. The cluster spec contains a kubernetesVersion, so you can simply edit it with kops edit, and apply the updated configuration to your cluster.

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.

Manual update

  • 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 update cluster $NAME --yes
  • 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

In future the upgrade step will likely perform the update immediately (and possibly even without a node restart), but currently you must:

For kOps 1.31 and newer, run kops reconcile cluster $NAME --yes

For older kOps versions, run:

  • 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

For more detail about the command change in kOps 1.31, see docs/tutorial/upgrading-kubernetes.md.

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

Terraform Users

  • kops edit cluster $NAME
  • 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.