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

From 3.0 Alpha

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

The 3.0 beta is almost ready, so we’ve rolled out the new jx-requirements.yml file format which uses API versioning and removes lots of old deprecated content.

Your cluster git repository will be upgraded automatically when you upgrade your cluster via the jx gitops upgrade command inside a git clone of your cluster git repository.

NOTE once you upgrade your cluster you will also need to make sure all the quickstarts and imported projects are using the latest pipelines from the catalog to ensure the container images are at least at 3.0 beta level.

From 2.x

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

If you wish to migrate from older versions of JayeX to v3 we recommend spinning up a new cluster for v3 and then incrementally moving projects from the old cluster to the new cluster.

This might sound heavy handed but the issue with working with multiple versions of a number of charts like lighthouse and tekton is that they use cluster scoped resources (CRDs and clusterrole resources for example) which can compete with each other. e.g. installing a new version of a chart may well break an old installation.