omni icon indicating copy to clipboard operation
omni copied to clipboard

[bug] Workload exposer DNS not resolving

Open neilmfrench opened this issue 1 year ago • 6 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Current Behavior

Exposed workload does not resolve. After exposing a workload, I see it listed in the Omni cluster UI, but when clicking it the webpage does not resolve due to DNS:

Expected Behavior

Proxied workload to resolve

Steps To Reproduce

  1. Expose workload in cluster via annotations
            omni-kube-service-exposer.sidero.dev/port: "50080"
            omni-kube-service-exposer.sidero.dev/label: Hubble
  1. Click on workload in Omni UI -> brings me to a webpage https://p-7z6vhs-omni.{my domain}/
  2. Workload does not resolve: server IP address could not be found.

What is this domain supposed to point to?

What browsers are you seeing the problem on?

Chrome

Anything else?

No response

neilmfrench avatar Apr 01 '24 18:04 neilmfrench

There is a bug that DNS takes some time to propagate, it will work, just give it a bit of time. It will be fixed in #17 .

smira avatar Apr 01 '24 18:04 smira

I've had the service up for multiple days. Conceptually I don't understand how I could ever resolve that domain - what DNS server has the correct record for it? CoreDNS on the cluster?

neilmfrench avatar Apr 01 '24 23:04 neilmfrench

Ah, you're running yourself. In that case you would need an addon to handle that. I don't think we have that documented at the moment.

smira avatar Apr 02 '24 09:04 smira

I have the same issue. Any idea when the add on would be released?

ohurvitz avatar May 05 '24 20:05 ohurvitz

I have the same issue. Any idea when the add on would be released?

We would eventually get there, but unfortunately we cannot give a date for that atm.

utkuozdemir avatar May 06 '24 07:05 utkuozdemir

I have the same issue. Any idea when the add on would be released?

We would eventually get there, but unfortunately we cannot give a date for that atm.

I think I can solve this for now by putting Omni in its own subdomain with a wildcard cname so all names point to it. I'll use dashboard.omni.[domain] for the dashboard. I'll use a wildcard certificate and see how it goes.

ohurvitz avatar May 06 '24 13:05 ohurvitz