Skip to content
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

Devfile and Plugin Registries define its own domain even when default/single mode is configured #14564

Closed
leader-us opened this issue Sep 17, 2019 · 12 comments
Labels
area/devfile-registry area/install Issues related to installation, including offline/air gap and initial setup area/plugin-registry kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@leader-us
Copy link

With the latest master version , I can deploy single-host mode successfully .
Can I deploy Che using ingress gateway's IP address instead of domain ? for example ,set global.ingressDomain=192.168.18.30 instead of mychedomain

@leader-us leader-us added the kind/question Questions that haven't been identified as being feature requests or bugs. label Sep 17, 2019
@leader-us
Copy link
Author

test

obviously devfile-registry-default.192.168.18.3 is not a valid IP

@l0rd
Copy link
Contributor

l0rd commented Sep 17, 2019

@leader-us I guess that it should be possible but @sleshchenko can be more precise.

Anyway it looks like in your screenshot you are not using single-host. Can you provide more information about how you have deployed Che (chectl, helm chart, operator, minishift-addon?) and what's the versions of kubernetes .

@l0rd l0rd added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Sep 17, 2019
@sleshchenko
Copy link
Member

Adding @metlos since he worked on Single/Default host mode support.

@leader-us
Copy link
Author

@metlos @l0rd I use Helm to deploy Che on kubernetes v1.15.2 . I saw ingress yarn file of devfile-registry and plugin-registry , the host name is prefix+ingressdomain .

@leader-us
Copy link
Author

@l0rd @sleshchenko @Fabs @metlos
I try to modify devfile-registry's ingress yaml ,so I can use ingress gateway's ip and subpath to access it ,for example
image

so I can access devfile-registry as following

image

but when i access che from browser ,I find it use https instead of http ,so some error occurred !
image

@sleshchenko
Copy link
Member

you're not able to just modify ingress since some certificate is already assigned to it...
Could you share full helm command that you run to get Che deployed? I guess it may be a bug...

@sleshchenko
Copy link
Member

Seems that Plugin Registry and Devfile Registry helm charts do not respect in the same way as Che and Keycloak do

@sleshchenko sleshchenko added kind/bug Outline of a bug - must adhere to the bug report template. area/devfile-registry area/plugin-registry and removed kind/question Questions that haven't been identified as being feature requests or bugs. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Sep 19, 2019
@leader-us
Copy link
Author

helm install -n myche -f ./values/default-host.yaml .
global:
multiuser: true
ingressDomain: 192.168.18.3
serverStrategy: single-host

[root@k8s_lab che]# helm install -n myche -f ./values/default-host.yaml .
Error: release myche failed: Ingress.extensions "keycloak-ingress" is invalid: spec.rules[0].host: Invalid value: "192.168.18.3": must be a DNS name, not an IP address

so I try modified some yarm files to install and Plugin Registry and Devfile Registry helm ingress can't work properly

@sleshchenko sleshchenko changed the title Can I deploy Che using ingress gateway's IP address instead of domain ? Devfile and Plugin Registries define its own domain even when default/single mode is configured Sep 25, 2019
@che-bot
Copy link
Contributor

che-bot commented Mar 25, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 25, 2020
@che-bot che-bot closed this as completed Apr 1, 2020
@metlos metlos reopened this Apr 2, 2020
@metlos metlos removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 2, 2020
@tolusha tolusha added this to the Backlog - Deploy milestone May 28, 2020
@l0rd l0rd added the area/install Issues related to installation, including offline/air gap and initial setup label May 31, 2020
@tolusha tolusha mentioned this issue Jun 1, 2020
34 tasks
@tolusha tolusha modified the milestones: Backlog - Deploy, 7.15 Jun 3, 2020
@l0rd l0rd added the severity/P1 Has a major impact to usage or development of the system. label Jun 8, 2020
@mmorhun mmorhun mentioned this issue Jun 23, 2020
14 tasks
@tolusha
Copy link
Contributor

tolusha commented Jun 30, 2020

#17149

@tolusha
Copy link
Contributor

tolusha commented Jul 15, 2020

Issue is fixed by:
#17392
eclipse-che/che-operator#341

We still have problem with starting workspaces in single-host mode #17396

@tolusha tolusha closed this as completed Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-registry area/install Issues related to installation, including offline/air gap and initial setup area/plugin-registry kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants