-
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
workspace namespace/project placeholders #14524
Conversation
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Tested with oauth on Minishift OS3.11. Creates namespace/project fine. |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
ci-build |
Q:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
So, these placeholders may work in such cases:
There is an issue (or at least there were discussions) to remove cluster-admin permissions for k8s installation, but currently, Che has such permissions by default https://github.com/eclipse/che/blob/master/deploy/kubernetes/helm/che/templates/cluster-role-binding.yaml |
works fine on minikube. As @sleshchenko mentioned, it will stop working when we remove cluster-admin permission. |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
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.
in general looks good
this.serviceAccountName = serviceAccountName; | ||
this.clusterRoleName = clusterRoleName; | ||
this.clientFactory = clientFactory; | ||
} | ||
|
||
private boolean hasPlaceholders(String namespaceName) { | ||
for (String placeholder : NAMESPACE_NAME_PLACEHOLDERS.keySet()) { |
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.
wdyt may be stream-based implementation would look clener?
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.
might be, I don't have strong preference here. I've changed it to stream, but kept it in own method.
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
Selenium tests execution on Eclipse Che Multiuser on OCP (https://ci.codenvycorp.com/job/che-pullrequests-test-ocp/2316//Selenium_20tests_20report/) doesn't show any regression against this Pull request. |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
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.
LGTM
...rg/eclipse/che/workspace/infrastructure/kubernetes/namespace/KubernetesNamespaceFactory.java
Show resolved
Hide resolved
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
ci-build |
...rg/eclipse/che/workspace/infrastructure/kubernetes/namespace/KubernetesNamespaceFactory.java
Show resolved
Hide resolved
I've tested with |
What does this PR do?
Adds possibility to use placeholders in namespace for workspace with current-user values. There are currently 2 placeholders
<username>
and<userid>
.<something>
pattern is not definitive. Please comment in case of any concerns or better ideas.What issues does this PR fix or reference?
#13488
Docs PR
no docs describing installation and workspace strategies exists yet.