Open gilsdav opened 4 years ago
@gilsdav CLI will always wait for dashboard to have https link, which means you have either enable lets encrypt or provide your own certs. Dashboard doesn't work at this time if accessed with http protocol. If you really want the http link, rio -s ps
should give you the link.
@StrongMonkey Thank's for your answer.
I didn't know the -s
. I tried to access to the http dashboard but get a 503
. Probably because the CLI never did all it's job (after it detect the https).
I will try to add celf-sign certificate. Do you have an ressource/documentation to add it easily ?
Two places you can add
Thanks
I tried to add secretName: default-tls
into the existing ClusterDomain (with rio rdns) after creating this secret. But nothing changed :/ Https seems not to be enabled.
Wildcard certificates: ....on-rio.io(false)
Describe the bug
I installed RIO on local k3s cluster. The only option that is not compatible with local cluster is lets-encrypt so I don't have https.
Service deployment works fine with good on-rio.rio sub domain.
I can see here that we must have https to access to the dashboard. I have now an infinit
Waiting for dashboard service to be ready
No AppEndpoints found in the dashboard service status. Only have (with this command:
kubectl edit svc dashboard -n rio-system
):To Reproduce
rio dashboard
Expected behavior
Get an http link of the dashboard if let-encrypt is disabled (
"letsencrypt":{"enabled":false,"description":"Let's Encrypt"}
inrio-config
configMap).Kubernetes version & type (GKE, on-prem):
kubectl version
Type: Rio version:
rio info