Allows you to upgrade existing deployments in Rancher 2 in your CI process. This image will use the Rancher CLI to change an environment variable, which will cause kubernetes to re-pull the docker image. ai-rancher2-upgrade would not be necessary if the Rancher 2 CLI would allow specifying the project ID. In this case it would be a 2-liner to upgrade a service. But since the Rancher 2 CLI currently has no non-interavtive mode, it will ask the user to select a project if there is more than just the default project. This image picks up the work-around suggested in rancher/rancher#14448. It writes a cli2.json file based on environment variables which contains the authentication data and project it.

1. Specify the following environment variables (e.g. in Gitlab > CI/CD > Variables"):

• RANCHER2_ACCESS_KEY (From Rancher 2 "API & Keys")
• RANCHER2_SECRET_KEY (From Rancher 2 "API & Keys")
• RANCHER2_SERVER_URL (The URL of your Rancher 2 deployment)
• RANCHER2_PROJECT_ID ("View in API" next to project, then the property "id")

2. Run the docker-entrypoint.sh (gitlab will not do this automatically). This will create the cli2.json

3. Execute "upgrade.de [namespace] [deployment]" script for each deployment, you want to upgrade.

Sample gitlab-ci.yml:

deploy to test:
  stage: deploy
  image: ambientinnovation/rancher2-upgrade:v1.0.0
  variables:
    GIT_STRATEGY: none
  only:
    - develop
  script:
    - /usr/local/bin/docker-entrypoint.sh # Creates the cli2.json with authentication data
    - /usr/local/bin/upgrade.sh default website # Triggers the actual upgrade

This project is hosted at https://github.com/ambient-innovation/rancher2-upgrade The docker image is hosted on dockerhub.

To make changes, proceed as follows:

1. Make your changes to the code
2. $ docker login (Credentials in 1 Password)
3. $ docker build -t ambientinnovation/rancher2-upgrade:v1.0.0 .
4. $ docker push ambientinnovation/rancher2-upgrade:v1.0.0