Update migration-guide-v1alphav1-to-v1alpha2.md

This commit is contained in:
Paweł Prażak 2019-06-19 15:49:49 +02:00 committed by GitHub
parent a0b04318dc
commit 877999f7a1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions

View File

@ -1,5 +1,8 @@
# Migration guide from v1alpha1 to v1alpha2 # Migration guide from v1alpha1 to v1alpha2
Please not that **CRD manifests are global**, not namespaced, so every jenkins operator running on the cluster
will be impacted by the new CRD manifest.
## Stop jenkins-operator pod ## Stop jenkins-operator pod
Run command: Run command:
@ -50,7 +53,7 @@ spec:
master: master:
basePlugins: basePlugins:
- name: a-plugin-name - name: a-plugin-name
version: 1.0.0 version: "1.0.0"
... ...
``` ```
- `spec.master.plugins` example: - `spec.master.plugins` example:
@ -60,7 +63,7 @@ spec:
master: master:
plugins: plugins:
- name: a-plugin-name - name: a-plugin-name
version: 1.0.0 version: "1.0.0"
... ...
``` ```
@ -316,9 +319,9 @@ $ kubectl -n <namespace> apply -f https://raw.githubusercontent.com/jenkinsci/ku
## Deploy new operator manifests ## Deploy new operator manifests
Apply your modified operator configuration file: Replace your modified operator configuration file:
```bash ```bash
$ kubectl -n <namespace> apply -f jenkins.yaml $ kubectl -n <namespace> replace -f jenkins.yaml
``` ```
Update operator version in the deployment file to `image: virtuslab/jenkins-operator:v0.1.0` and scale up, Update operator version in the deployment file to `image: virtuslab/jenkins-operator:v0.1.0` and scale up,