-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update default plugin/devfile registries to use prod-preview #14267
Update default plugin/devfile registries to use prod-preview #14267
Conversation
Update the default registries used in che.properties to use the prod-preview deployments instead of production. This is to avoid issues where snapshot changes of registries and che defaults are incompatible with the deployment on production. Signed-off-by: Angel Misevski <amisevsk@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, this is step in right direction.
hmm... I thought the plan was not to use OSIO registries at all by default, but rather deploy them together with Che Server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it considered to be a temp solution?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds like a reasonable workaround for minishift addon case. But in general, I do believe upstream che should not fall back on osio plugin registries at all since it makes Hosted Che and Che release process dependent
@ibuziuk Yeah this is definitely to be a temporary solution, since rolling out nightlies of the registries will only work going forward if we somehow also roll out Che nightlies. I think that after all deployment methods are updated to deploy registries alongside Che, we should leave the |
What does this PR do?
Use https://che-plugin-registry.prod-preview.openshift.io and https://che-devfile-registry.prod-preview.openshift.io/ instead of their production equivalents.
What issues does this PR fix or reference?
#14266, #14261