Modifying "Launching the Kubesafe UI"
Hi @brian84 ,
For the main titles, you can replace Gluster
with OCS3-Gluster
For the update of this section, please, I suggest starting the "Launching the Kubesafe UI" with something like: "If you deployed Kubesafe in AWS, you access the Kubesafe UI through port 8080 at the IP address your load balancer assigns for the kubesafe-ui pod. This address might take several minutes to come up.
$ oc get svc kubesafe-ui -n kubesafe
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubesafe-ui LoadBalancer 172.30.53.164 a6dc6d97da5d411ebb53c02db7e5fa55-627344578.us-east-2.elb.amazonaws.com 8080:31526/TCP 7h
In this example, Kubesafe is available at:
https://a6dc6d97da5d411ebb53c02db7e5fa55-627344578.us-east-2.elb.amazonaws.com:8080
If you deployed Kubesafe on premises, you access the Kubesafe UI through the name and port number assigned to the kubesafe-ui service... "
What do you think? Thanks