Upgrades on JayeX - Cloud Native CI/CD Built On Kubernetes

CLI

Mon, 01 Jan 0001 00:00:00 +0000

CLI

To upgrade the jx CLI run:

jx upgrade cli

To upgrade jx subcommand plugins run:

jx upgrade plugins

Note

If you encounter this error:

ERROR: failed to load plugin <plugin-name>: can't find latest version of plugin: {"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#get-the-latest-release"}

Then most probably it’s an old plugin which is not maintained, and can be removed from ~/.jx3/plugins/bin folder.

The jx CLI version used to upgrade to is derived from the JayeX version stream.

Cluster

Mon, 01 Jan 0001 00:00:00 +0000

Cluster

Automatic upgrades

To enable automatic upgrades of your cluster you need to modify your jx-requirements.yml file in your development git cluster repository:

apiVersion: core.jenkins-x.io/v4beta1
kind: Requirements
spec:
  autoUpdate:
    enabled: true
    schedule: "0 0 * * *"
    autoMerge: true

Once you commit and push that change and your boot job has completed you should have a CronJob running at the above schedule (every night at midnight) creating a Pull Request to upgrade your cluster’s versions of charts and images.

Infrastructure

Mon, 01 Jan 0001 00:00:00 +0000

Infrastructure

If you have used one of the JayeX Terraform Git repositories to create and manage your cloud resources then you have two options.

Terraform manual apply

If you are running the Terraform apply commands yourself then from your infrastructure Git repository run:

export TF_VAR_jx_bot_username=[your bot username]
export TF_VAR_jx_bot_token=[your bot token]
terraform get -update
terraform plan
terraform apply

Terraform Cloud

If you are using Terraform Cloud then from your infrastructure Git repository run:

LTS

Mon, 01 Jan 0001 00:00:00 +0000

WARNING: The LTS is not updated, so we don't recommend using it

JayeX uses version streams as a quality gate when promoting plugins, charts, cli packages, container images etc. This results in a release of JayeX.

The default version stream for JayeX 3.x is https://github.com/jenkins-x/jx3-versions. The JayeX own infrastructure runs a number of end to end BDD tests for different base install options which covers the core of JayeX. Provided these tests pass on from a Pull Request it will be merged and users can upgrade their CLI and Cluster bringing in the versions that make that release.

Version Stream Manual Migrations

Mon, 01 Jan 0001 00:00:00 +0000

Version Stream Manual Migrations

The sections below document manual migration steps required that occur from time to time where an automated upgrade is not possible or practical

v0.0.969

NB: These steps are only relevant if you are using Hashicorp Vault as secret storage within jx. Ignore for all other secret stores

v0.0.969 introduced a change to remove Hashicorp Vault from jx control and become an explicit cluster dependency installed either via Terraform (for cloud environments) or Helm (for on-premises). The reasoning behind this is to reduce cyclic complexity within jx where the platform requires secrets and the jx platform is also responsible for provisioning where to store these secrets.