-
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
[chectl] Be more specific in the help about the --domain option #14404
Comments
The latest info about --domain parameter is the following:
Actually, you do not have to specify a domain for OpenShift installation since it's totally ignored. But I think it makes sense to keep this issue and maybe UX even better and make it clear that it's unneeded for OpenShift. cc @benoitf |
In the Is there a way to install latest (unreleased) version of che-incubator/chectl to install the released versions of eclipse/che? The README.md for chectl is not absolutely clear: "Next is updated after each commit/Pull Request being merged in master branch." Could it be specified if it is the master branch of eclipse/che or of che-incubator/chectl? |
@themr0c domain is mandatory for k8s/openshift but it's not for minikube/minishift.
By default, unreleased version of
thx for reporting. It's updated after each commit inside chectl. Do you want to propose a PR to improve it ? |
Added extended description into |
Context:
After the installation of Code-Ready containers, the user has knowledge of these two URLs:
Then he needs to fill in a domain option to start a Che server.
The current documentation of the
--domain
option when usingchectl --help
is not specific enough to help the user choose the right domain.For a crc, instance, correct value would be
--domain=.apps-crc.testing
.In other usecases, the user should be helped to decide which domain would be the right one.
Thanks @benoitf fot all the hints.
The text was updated successfully, but these errors were encountered: