whereabouts
whereabouts copied to clipboard
A CNI IPAM plugin that assigns IP addresses cluster-wide
**What this PR does / why we need it**: When configuring `enable_overlapping_ranges` in the pod-configuration (e.g. by using a multus `NetworkAttachmentDefinition`, the parsing of the configuration makes an error. This...
Remove the `controller-runtime` dependency from the project. Simplifies upgrading k8s dependencies going forward. Depends-on: #265
**What this PR does / why we need it**: Whenever the docs folder - or the README - changes, there is no need to run the unit tests, nor the...
As requested [here](https://github.com/k8snetworkplumbingwg/whereabouts/issues/50#issuecomment-1205035504) this is a proposal for named networks to allow using the same CIDR range for multiple networks (e.g. in multi-tenancy situations). Cc @maiqueb
**Describe the bug** when a node is restarted the Whereabouts pod starts but the network controller fails to connect to the k8s API and retrieve the network-attachment-definitions. The pod continues,...
# New Feature ## Motivation This PR adds support for IPv4/IPv6 dual-stack and multiple IP assignment Feature proposal: #237 ## Changes - Introduced a new type `RangeConfiguration` in `pkg/types/types.go` for...
**Describe the bug** The `"range"` configuration parameter allows addresses in a from-to format, e.g. ``` "range": "2001:d3ad:b33f:f00d:d00d:d00d:000:0000-2001:d3ad:b33f:f00d:d00d:d00d:0000:0004/64", ``` Which would allocate 5 IPv6 addresses. Some IPv6 addresses however, wind up...
**Describe the bug** Cronjob to release free ips are not getting executed on scheduled interval. **Expected behavior** Cronjob to clear free ips into the pool must have executed as per...
**Describe the bug** with k8s 1.22 I'm able to see/get more and more issues like Memory cgroup out of memory: Killed process 643039 (ip-control-loop) total-vm:742792kB, anon-rss:43452kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:240kB...
**What this PR does / why we need it**: This allows specifying an optional `network_name` in the IPAM-config as such: ```json { "cniVersion": "0.3.1", "name": "meganet", "type": "bridge", "bridge": "meganet",...