support IP SAN (IPv4 advertised address) for controller package and container image

openziti / ziti

The parent project for OpenZiti. Here you will find the executables for a fully zero trust, application embedded, programmable network @OpenZiti

https://openziti.io

Apache License 2.0

2.88k stars 162 forks source link

support IP SAN (IPv4 advertised address) for controller package and container image #1993

Open qrkourier opened 7 months ago

qrkourier commented 7 months ago

Clint says the Linux package for the controller needs to support an IP address, not require an FQDN, for the controller address in this comment: https://github.com/openziti/ziti-doc/pull/820#discussion_r1580013693

I think there's a way to do that with the built-in config generator, but haven't explored it yet.

I extrapolated the requirement to include routers and container images too.

dovholuknf commented 7 months ago

look at expressInstall. It does this. there are plenty of cloud vendors that don't provide DNS entries by default. there are numerous users using "IP-based" installs from OCI for example.

dovholuknf commented 7 months ago

this issue can be closed imo. maybe i'm missing something?

qrkourier commented 7 months ago

This issue will be resolved when the Linux packages and container images support using an IP address instead of FQDN. It's not something I'd ever recommend for production, but we can support it as a follow up enhancement.

qrkourier commented 3 months ago

I confirmed the router already handles the advertised address of the controller or its own address as an IP address without further configuration, so this issue pertains only to supporting IP SAN for controller deployments.