Skip to content
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.

Steps for Bumping Kubernetes

Urvashi Reddy edited this page Nov 7, 2018 · 2 revisions

Create a issue in kubo-release titled: "Bump Kubernetes to version: [version]". Copy the checklist below into the body of the issue. Close the issue when you're done!

  • Create config/private.yml in kubo-release to upload blobs. The credentials are in lastpass.

  • Run the script in kubo-release to download the k8s binaries

    • ./scripts/download_k8s_binaries 1.12.2
  • Check the git diff to make sure the script ran correctly. You should see:

    • config/blobs.yml updated with new blobs of the specified version. Corresponding old blobs should have been removed.
    • packages/kubernetes/spec and packages/kubernetes/packaging should have been updated to the specified version
    • the script will also create backup copies titled: packages/kubernetes/packaging-e & . packages/kubernetes/spec-e. These can be ignored if the script did its job correctly.
  • Deploy the changes to a CFCR cluster. Preferably a cluster that is already running and can test the upgrade path.

  • Run smoke-tests and the apply-addons errand to make sure they still work.

  • Fix or create stories for any changes that need to happen. Tip: sometimes the deploy will succeed however the component may be silently failing. Its good practice to check the logs of the major components to make sure things are running.

  • Once confident about the changes, run bosh upload-blobs and commit the changes. It may be appropriate to create a branch off develop and file a PR.

  • Remove config/private.yml

Clone this wiki locally