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.

Sign up for GitHub

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

Jump to bottom

[devworkspace] Not able to deploy workspace-controller on local crc #16314

Closed
sleshchenko opened this issue Mar 11, 2020 · 0 comments · Fixed by devfile/devworkspace-operator#26
Closed

[devworkspace] Not able to deploy workspace-controller on local crc #16314

sleshchenko opened this issue Mar 11, 2020 · 0 comments · Fixed by devfile/devworkspace-operator#26
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Mar 11, 2020 •
edited
Loading

Is your task related to a problem? Please describe.

Not able to deploy workspace-controller on local crc.

  1. crc setup configures dnsmasq locally in the way that the internet in not available from docker anymore, so ./deploy/webhook-server-certs/deploy-webhook-server-certs.sh fails with error :
Step 2/5 : RUN apk add --no-cache openssl
 ---> Running in b6ff705ef87b
fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz: temporary error (try again later)

It should not be actual when #16251 is fixed.

Fixing crc setup breaks local networkingcrc#1095 would fix the issue as well.

  1. ^ it's possible to work around that issue by manual editing /etc/resolv.conf. But then you must modify ingress hosts, which is kind of expected but not really convenient and required in case of OpenShift... We could create Route instead of Ingress with empty host and it will be provisioned automatically.

  2. It's not possible to run workspaces from non-admin user... Probably in our deploy files we must add some default role that will allow users to manage workspaces in their namespaces.
    Screenshot_20200311_124235

  3. kubectl is not actully requirement for openshift... So, our deployment should be able to use oc as well.
@sleshchenko sleshchenko added kind/task Internal things, technical debt, and to-do tasks to be performed. engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. labels Mar 11, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 11, 2020
@sleshchenko sleshchenko added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 11, 2020
@sleshchenko sleshchenko mentioned this issue Mar 20, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix deploying on OpenShift 4.x sleshchenko/devworkspace-operator
2 participants
@sleshchenko @che-bot