Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1174

Improve crwctl downstreamed doc - remove k8s and kube items, clarify multiuser mode, etc.

XMLWordPrintable

      In https://github.com/redhat-developer/codeready-workspaces-chectl#user-content-crwctl-serverstart, there are a few references to minikube and microk8s which should be removed.

        -b, --domain=domain
            Domain of the Kubernetes cluster (e.g. example.k8s-cluster.com or <local-ip>.nip.io)
                                 This flag makes sense only for Kubernetes family infrastructures and will be autodetected for 
            Minikube and MicroK8s in most cases.
                                 However, for Kubernetes cluster it is required to specify.
                                 Please note, that just setting this flag will not likely work out of the box.
                                 According changes should be done in Kubernetes cluster configuration as well.
                                 In case of Openshift, domain adjustment should be done on the cluster configuration level.
      

      Another example from https://github.com/redhat-developer/codeready-workspaces-chectl#user-content-crwctl-serverstop and https://github.com/redhat-developer/codeready-workspaces-chectl#user-content-crwctl-serverupdate:

        -n, --chenamespace=chenamespace          [default: workspaces] Kubernetes namespace where CodeReady Workspaces server
                                                 is supposed to be deployed
      

      Also, I was under the impression that CRW is ONLY deployed in multi-user mode, so we should either remove that flag, or clarify that it's on by default (like --tls used to be).

        -m, --multiuser
            Starts CodeReady Workspaces in multi-user mode

            abazko Anatolii Bazko
            nickboldt Nick Boldt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: