Change the domain of the service proxy when self hosting?

[Nikola-Milovic]

Hey everyone,

Trying to use the service proxy feature for omni instance that's being self host and ran on omni.example.com

The proxy URL I get is https://openbao-omni.proxy-us.example.com/

    ui:
      annotations:
        omni-kube-service-exposer.sidero.dev/port: "50082"
        omni-kube-service-exposer.sidero.dev/label: OpenBao
        omni-kube-service-exposer.sidero.dev/icon: "H4sICGMug2kAA29wZW5iYW8tY29..."
        omni-kube-service-exposer.sidero.dev/prefix: openbao

Is it possible to change this?

Ideally the format would be https://prefix/service_name.cluster_name.omni_domain. So I could set something like

omni-kube-service-exposer.sidero.dev/name: openbao

And it would be https://openbao.staging-cluster.omni.example.com?

This inclusion of the cluster is more of a feature request, my actual question is how can I change the proxy-us, it seems internal to the SaaS version of omni, and ideally it would be configurable if its not already

[utkuozdemir]

Hi Nikola,

We recently added some documentation on how to configure workload proxying in a self-hosted setup, in our Helm chart v2 docs: https://github.com/siderolabs/omni/tree/main/deploy/helm/v2/omni#workload-proxy-optional

You do not need to use the new chart to configure workload proxying - you can just read it to better understand how it works. The value can also be configured via --workload-proxying-subdomain CLI flag.

We have plans to make it more flexible, i.e., allow any domain to be used, but not ETA for that.

[utkuozdemir]

Created #2280 to track that.

[Nikola-Milovic]

Awesome @utkuozdemir Thank you!