-
Notifications
You must be signed in to change notification settings - Fork 165
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
procedures: Configuring workspace target namespace, Provisioning namespaces #2301
Conversation
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspaces-globally.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
…ally.adoc Co-authored-by: Ilya Buziuk <[email protected]>
Tested with Che on Minikube. However, I am not sure how to reproduce the prerequisite "The workspace user cannot create namespaces on {orch-name}." for the second procedure. (Meaning that step 1 is sufficient). Therefore, for the next steps, the current state reflects what is created in nominal conditions. |
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 is great @themr0c. It's clear and goes straight to the point. I have added a few comments.
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
Applied suggestions. Ready for language review I think. |
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.
Fantastic 👍
modules/administration-guide/pages/configuring-namespace-provisioning.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces-in-advance.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/provisioning-namespaces-in-advance.adoc
Outdated
Show resolved
Hide resolved
modules/administration-guide/pages/configuring-workspace-target-namespace.adoc
Outdated
Show resolved
Hide resolved
…advance.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…advance.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…sioning.adoc Co-authored-by: Brian Burt <[email protected]>
…t-namespace.adoc Co-authored-by: Brian Burt <[email protected]>
…spaces (eclipse-che#2301) Co-authored-by: Ilya Buziuk <[email protected]> Co-authored-by: Brian Burt <[email protected]>
Configuring workspace target namespace, Provisioning namespaces
references: eclipse-che/che#21284
What does this pull request change
Update configuring-namespace-strategies
What issues does this pull request fix or reference
Remove "namespace strategy" concept.
Refresh with current situation.
Specify the version of the product this pull request applies to
Pull request checklist
The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.
Validate language on files added or modified
step reports no vale warnings.