After updating CheCluster CR Che is in an inconsistent state
See original GitHub issueDescribe the bug
When creating a Che server though the Operator with the default settings (which now also includes deploying embedded registries), and then enabling TLS, the Che server is broken:
- Openshift OAuth login is broken since Openshift
OAuthClient
confirguation is not updated with the newhttps
-based redirect URL - The devfile list and plugin brokering are broken since the routes of the embedded registries are not upgraded to TLS.
Additionally, a problem related to CheCluster
update logic break the correct use of devfileRegistryUrl
and pluginRegistryUrl
values, so that only the default registry URLs (those on openshift.io
) can be used when external registries have been set in the custom resource at creation time.
Che version
- latest
- nightly
- other: please specify
Steps to reproduce
-
TLS-related error:
- Create a Che Cluster with default settings with the Operator
- Enable TLS and self-signed certificates in a second steps
-
Registry related error:
- Create a
CheCluster
resource withexternalDevfileRegistry
set to true andexternalDevfileUrl
set to a custom URL - The started Che server will use the
che-devfile-registry.openshift.io
URL for the devfile registry instead of your custom URL
- Create a
Expected behavior
- Changing the
CheCluster
custom resource to enable TLS and self-signed certificates should behave correctly, especially knowing that enabling TLS can be done from the OperatorHub UI through a switch. - External plugin registry URL should taken into account.
Runtime
- kubernetes (include output of
kubectl version
) - Openshift (include output of
oc version
) - minikube (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Installation method
- chectl
- che-operator
- minishift-addon
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- other: please specify
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Chapter 2. Configuring the CodeReady Workspaces installation
Apply the CheCluster Custom Resource YAML file with suitable modifications in the server component section. The Operator generates the che ConfigMap . OpenShift ......
Read more >Using chectl to configure the CheCluster Custom ... - Eclipse
Create a che-operator-cr-patch.yaml YAML file that contains the subset of the CheCluster Custom Resource to configure: · Deploy Che and apply the changes ......
Read more >The Complex Transcriptional Landscape of Magnetosome ...
Under standard conditions, the cells had an inconsistent phenotype, with most cells having regular magnetosomes and a minor proportion ...
Read more >eclipse-che 7.57.0 - Artifact Hub
Apply CR: $ kubectl apply -f org_v2_checluster.yaml -n eclipse-che. Also, you can use kubectl edit checluster/eclipse-che -n eclipse-che to update Eclipse ...
Read more >80 IP 30" 67 DEF I - Town of Sudbury
State Election. State Primary. State of the Town. Street Acceptances. Becknith Street. Guzzl,ebrook Drive. Hawes Road. Maynard Farn Circle.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s linked above, @slemeur but here you go: https://github.com/eclipse/che-operator/pull/63
Yes