Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
qrkourier opened this issue Apr 29, 2024 · 3 comments

Comments

@qrkourier
Copy link
Member

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: openziti/ziti-doc#820 (comment)

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
Copy link
Member

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
Copy link
Member

dovholuknf commented Apr 29, 2024

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

@qrkourier
Copy link
Member Author

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 qrkourier changed the title support IPv4 address for controller and router package and container image support IP SAN (IPv4 advertised address) for controller and router package and container image May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants