Known issues
Upgrading from Che 6 to Che 7 using the Operator
When upgrading the Operator of a Che 6 installation to Che 7, some components may not be automatically updated. To fix this, manually update the images listed in the checluster custom resource, which describes the Che installation. To reset the images to their default versions for given operator version, set the image properties to empty strings. This forces the Che Operator to use the default versions it was built with.
Review the following components:
Component |
CR attribute name |
Postgresql |
|
Keycloak |
|
PVC Jobs |
|
Updating a Che installation using the Operator
When making changes to the checluster custom resource, use patching to make updates to it. For example:
On Kubernetes, run:
$ kubectl patch checluster <my-che> --type=json -n <che-namespace> -p '...'
On OpenShift, run:
$ oc patch checluster <my-che> --type=json -n <che-namespace> -p '...'
Making local updates to the YAML file of the checluster resource and then applying such changed resource to
the cluster using kubectl apply -f or oc apply -f can result in an invalidation of the Che installation.
|