You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The service cluster IP range is hardcoded to 10.32.0.0/24. I'm guessing we should make this a parameter, with a default value instead?
Also, why /24? Doesn't this limit the number of services in the cluster to 256? I see that Kubernetes default is 10.0.0.0/24 though, so maybe it's common.
The text was updated successfully, but these errors were encountered:
@anton-johansson I would not call it hardcoded CID since this is working and you reconfigure @amimof ansible template for your own needs if you play with it.
Well, I guess it depends on how we want KTRW to be used. I don't want to use it as a template, because I want to be able to easily get upstream changes to KTRW (with a simple git pull).
I want to use it more as an application, where I can just configure things as I need through the Ansible inventory file. Otherwise, we might aswell remove all configurable options. :)
Anyway, I haven't hit any issue with 10.32.0.0/24, but I imagine that I will in the future, since it's limited to 256 (254?) services.
The service cluster IP range is hardcoded to
10.32.0.0/24
. I'm guessing we should make this a parameter, with a default value instead?Also, why
/24
? Doesn't this limit the number of services in the cluster to 256? I see that Kubernetes default is10.0.0.0/24
though, so maybe it's common.The text was updated successfully, but these errors were encountered: