-
Notifications
You must be signed in to change notification settings - Fork 72
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
Pool independent IPs #52
Comments
A new variable AllNodePools was introduced. Defaults to False. Once set to true all node pools in the cluster will be monitored and will get an available static ip from the pool Fixes #52
@geekflyer A new variable AllNodePools was introduced. Defaults to False. Once set |
@avivl I just tried out the latest version of kubeip and unfortunately this still doesn't work.
I think the problem lies here: kubeip/pkg/kipcompute/compute.go Lines 88 to 93 in 576fb60
The logic there is still filtering for IPs which are labeled with the target pool name. |
created a PR #54 which should fix this |
@geekflyer thanks good catch! |
We have a gke cluster with multiple node pools. We would like to assign static IPs to all nodes in the cluster.
Currently it seems the only way to achieve this is to reserve multiple static IPs and then exlusively pre-allocate each IP to a specific nodepool via the
kubeip-node-pool=<pool_name>
label.This is kind of problematic since whenever we change the number of pools or rename pools (sometimes it's necessary to replace one pool with another in order add for example a new oauth permission etc.) we also have to update the labels of all static IPs used in that cluster.
Would it be possible to simply have a single / cluster-wide "pool of ip addresses" which is used to satisfy the static IP address needs of multiple or all node pools in a specific cluster?
I.e. imagine this:
kubeip: <clusterName>
I'm fine still having to specify KUBEIP_NODEPOOL and KUBEIP_ADDITIONALNODEPOOLS if that's really required but it'd like to avoid "exlusively" tying a set of IPs to a single nodepool.
The text was updated successfully, but these errors were encountered: