From 82f058a7e7c2c6a2605f368cd6b78a45176f29ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Pra=C5=BCak?= Date: Sat, 4 Jan 2020 18:11:47 +0100 Subject: [PATCH] Create migration.md for 0.3.x (#241) Create migration.md --- .../docs/Getting Started/latest/migration.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 website/content/en/docs/Getting Started/latest/migration.md diff --git a/website/content/en/docs/Getting Started/latest/migration.md b/website/content/en/docs/Getting Started/latest/migration.md new file mode 100644 index 00000000..d151a4e0 --- /dev/null +++ b/website/content/en/docs/Getting Started/latest/migration.md @@ -0,0 +1,23 @@ +--- +title: "Migration from v0.2.x" +linkTitle: "Migration from v0.2.x" +weight: 10 +date: 2020-01-03 +description: > + How to migrate from v0.2.x to v0.3.x +--- + +### Changes + +- new Jenkins Custom Resource Definition version `jenkins.io/v1alpha2`: + - `spec.master.masterAnnotations` was deprecated, use `spec.master.annotations` + - added `spec.notifications` + - added `spec.master.tolerations` (in v0.3.1) + - added `spec.master.disableCSRFProtection` + +### Migration + +- adjust the operator image version, e.g. `image: virtuslab/jenkins-operator:v0.3.1` +- migrate your Jenkins Custom Resources to `apiVersion: jenkins.io/v1alpha2`, adjust content if necessary + +The v0.3.x should work fine with `jenkins.io/v1alpha1`, but we recommend using `jenkins.io/v1alpha2`.