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

Service cluster IP range/CIDR #58

Open
anton-johansson opened this issue Nov 10, 2019 · 3 comments
Open

Service cluster IP range/CIDR #58

anton-johansson opened this issue Nov 10, 2019 · 3 comments

Comments

@anton-johansson
Copy link
Collaborator

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.

@amimof
Copy link
Owner

amimof commented Feb 22, 2020

It's using whatever Mr Hightower was using :) I see that kubeadm init uses 10.96.0.0/12. https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/

@umbrellaLt
Copy link

@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.

@anton-johansson
Copy link
Collaborator Author

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.

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

3 participants