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

(feature) Shared IPAM IPRanges for both vips and vm ips #304

Open
lknite opened this issue Oct 18, 2024 · 0 comments
Open

(feature) Shared IPAM IPRanges for both vips and vm ips #304

lknite opened this issue Oct 18, 2024 · 0 comments
Labels
enhancement New feature or request kind/feature

Comments

@lknite
Copy link

lknite commented Oct 18, 2024

Describe the solution you'd like

When managing a workload cluster via cluster-api automate the assignment of the vip and vm ips.

On a namespace level:

  • one or more InClusterIPPool resources
  • label applied to InClusterIPPool resources: 'cluster-api-vips: true'
  • label applied to InClusterIPPool resources: 'cluster-api-vm-ips: true'
  • both labels may be applied to an InClusterIPPool resource

On a global level:

  • one or more GlobalInClusterIPPool resources
  • label applied to GlobalInClusterIPPool resources: 'cluster-api-vips: true'
  • label applied to GlobalInClusterIPPool resources: 'cluster-api-vm-ips: true'
  • both labels may be applied to a GlobalInClusterIPPool resource

Workflow

  • If namespaced InClusterIPPool resources are available in the ns where the cluster is deployed, use those to allocate vip and vm ips, based on labels.
  • If namespaced InClusterIPPool resources are available in the ns where the cluster is deployed, but are exhausted, fail with event out-of-vips, out-of-vm-ips, or out-of-vips-and-vm-ips
  • If no namespaced InClusterIPPool resources exist, use GlobalInClusterIPPool resources if available

Additional labels

  • Because more than one provider may be in use, and it may be desirable for all providers to use the same InClusterIPPools and/or GlobalInClusterIPPools, this can be enabled by applying the label 'cluster-api-allow-all-providers: true'
  • If someone wishes to use GlobalInClusterIPPool resources, if the namespaced InClusterIPPools resources are exhausted, this may be enabled by adding a label 'cluster-api-allow-overflow-vips: true' and/or 'cluster-api-allow-overflow-vm-ips: true'

Anything else you would like to add:

  • Allocating a vip is something that should be automated, in the same way that allocating a vm ip should be automated.
  • Would allow for VIP_IP_RANGES in the ~/.cluster-api/clusterctl.conf in addition to NODE_IP_RANGES.
  • Because labels are being used, this new feature would not break any existing implementations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request kind/feature
Projects
None yet
Development

No branches or pull requests

1 participant