-
Notifications
You must be signed in to change notification settings - Fork 130
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
adopt single-port default vars in ziti create config #1838
Comments
@dovholuknf and I decided on a set of config option variables to represent this single port default for generating configs.
|
Is this issue resolved? |
I think it depends on what you're looking for, the constants are all still the same values, so no it's not been changed to align to one port for controller, one for routers yet. see: ziti/ziti/constants/constants.go Lines 35 to 54 in 1c03219
But this is for the the config generator code. If you modify or make your own config file you can use a single port if you wish |
ziti create config controller
still uses the default TCP port 6262 for the control plane. Now that we have ALPN, a better default is to use a single TCP port 1280 for all default TLS listeners.The text was updated successfully, but these errors were encountered: