Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Installing RIO to an existing cluster isn't working as expected #1044

Open
Vad1mo opened this issue May 24, 2020 · 1 comment
Open

Installing RIO to an existing cluster isn't working as expected #1044

Vad1mo opened this issue May 24, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@Vad1mo
Copy link

Vad1mo commented May 24, 2020

I wanted to add rancher rio to an existing productive k8s cluster which has already linkerd, cert-manager installed. I want to use rio with linkerd/cert-manager but don't actually want rio to install those.

After installing rancher rio with rio install --disable-features "linkerd, rdns, letsencrypt"

  • I noticed that there was a RDNS on-rio.io domain assigned even that in config RDNS is false.
  • Starting the rio dashboard from the cli didn't work. (stuck in Waiting for dashboard service to be ready) The pod was up and running but there was no access to it (http/https)
  • I was able to create a service and bind it to my custom domain, like explained in the tutorial however I wasn't able to create a cert for that domain with the stock cert-manager.
@Vad1mo Vad1mo added the bug Something isn't working label May 24, 2020
@yuregir
Copy link

yuregir commented Nov 24, 2020

I am experiencing the same issue, I had to create wildcard certs by hand in another namespace, and copy to rio-system namespace, In 0.7 version everything was working as expected.

I am using this clusterDomain.yaml

image

This is temporary fix I found, I hope this will be fixed soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants