Kubernetes whereabouts IPAM 介绍

原创已于 2023-04-02 18:13:11 修改 · 947 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#kubernetes #CNI

于 2023-04-02 18:11:10 首次发布

Kubernetes 同时被 2 个专栏收录

24 篇文章

订阅专栏

CNI

6 篇文章

订阅专栏

Whereabouts是一个IP地址管理（IPAM）工具，用于替代host-localIPAM，支持在Kubernetes中记录和分配IP地址。它通过定义CRD（CustomResourceDefinition）如IPPool和OverlappingRangeIPReservation来管理IP资源。部署涉及创建NAD（NetworkAttachmentDefinition），然后通过Informer监听Pod、NAD和IPPoo资源的变化，动态分配和管理IP。当创建Pod时，会结合CNI二进制来处理IP的请求和释放。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

文章目录

Whereabouts

Whereabouts

是一款代替 host-local 的 IPAM，可以本地或用 kubernetes 记录 ippool 和已分配 IP；并且支持所有节点的 pod ip 可以使用同一个 cidr。
它是以 NAD 为地址段设定的模式，一个 nad 中描述该地址段的 ip 范围，网关等信息。
通常和cni bridge，ipvlan，macvlan 等相结合使用，负责分配和管理 IP 的功能。

部署

git clone https://github.com/k8snetworkplumbingwg/whereabouts.git
cd whereabouts
kubectl apply -f doc/crds/daemonset-install.yaml -f doc/crds/whereabouts.cni.cncf.io_ippools.yaml -f doc/crds/whereabouts.cni.cncf.io_overlappingrangeipreservations.yaml

CRD

overlappingrangeipreservations 所有分配的 IP
Ippool ippool 资源

服务

有一个 domainset 和 cni binary

Domainset 负责维护地址池
Cni binary，负责申请 IP

Informer

三个 informer listen pod，nad，ippool 三种资源
podInformerFactory.Start(stopChannel)
netAttachDefInformerFactory.Start(stopChannel)
ipPoolInformerFactory.Start(stopChannel)

流程

创建一个 nad

apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: whereabouts-conf
spec:
  config: '{
      "cniVersion": "0.3.0",
      "name": "whereaboutsexample",
      "type": "ipvlan",
      "master": "ens6",
      "ipam": {
        "type": "whereabouts",
        "datastore": "kubernetes",
        "range": "1.1.1.0/24",
        "range_start": "1.1.1.66",
        "range_end": "1.1.1.73",
        "gateway": "1.1.1.1",
        "log_file": "/var/log/whereabouts.log",
        "log_level": "debug"
      }
    }'

创建 pod 时

apiVersion: v1
kind: Pod
metadata:
  name: pod2
  namespace: default
  labels:
    app: nginx
  annotations:
    k8s.v1.cni.cncf.io/networks: default/whereabouts-conf
spec:
  containers:
  - name: pod2
    image: nginx
    ports:
    - name: nginx-port
      containerPort: 80
      protocol: TCP

Cni binary

cmdAdd 和 cmdDel 先解析 ipam 配置

ipamConf, confVersion, err := config.LoadIPAMConfig(args.StdinData, args.Args)

读取 ipRange

        oldRange := types.RangeConfiguration{
            OmitRanges: n.IPAM.OmitRanges,      // exclude
            Range:      n.IPAM.Range,           // range，可以 cidr，可以 "-" 隔开
            RangeStart: n.IPAM.RangeStart,
            RangeEnd:   n.IPAM.RangeEnd,
        }

cmdAdd 时先获取 ippool，如果没有则创建一个，其中 ippool 是根据 iprange 确定的，如 1.1.1.0/24 的 ippool name 就是 1.1.1.0-24

func (i *KubernetesIPAM) getPool(ctx context.Context, name string, iprange string) (*whereaboutsv1alpha1.IPPool, error) {
    ctxWithTimeout, cancel := context.WithTimeout(ctx, storage.RequestTimeout)
    defer cancel()

    pool, err := i.client.WhereaboutsV1alpha1().IPPools(i.namespace).Get(ctxWithTimeout, name, metav1.GetOptions{})
    if err != nil && errors.IsNotFound(err) {
        // pool does not exist, create it
        newPool := &whereaboutsv1alpha1.IPPool{}
        newPool.ObjectMeta.Name = name
        newPool.Spec.Range = iprange
        newPool.Spec.Allocations = make(map[string]whereaboutsv1alpha1.IPAllocation)
        _, err = i.client.WhereaboutsV1alpha1().IPPools(i.namespace).Create(ctxWithTimeout, newPool, metav1.CreateOptions{})
        if err != nil && errors.IsAlreadyExists(err) {
            // the pool was just created -- allow retry
            return nil, &temporaryError{err}
        } else if err != nil {
            return nil, fmt.Errorf("k8s create error: %s", err)
        }
        // if the pool was created for the first time, trigger another retry of the allocation loop
        // so all of the metadata / resourceVersions are populated as necessary by the `client.Get` call
        return nil, &temporaryError{fmt.Errorf("k8s pool initialized")}
    } else if err != nil {
        return nil, fmt.Errorf("k8s get error: %s", err)
    }
    return pool, nil
}

获取到 ippool 之后，根据已 allocate 的 ip 和 nad.ipam 地址段里的 ipstart-ipend 里分配一个可用 ip

newip, updatedreservelist, err := IterateForAssignment(*ipnet, ipamConf.RangeStart, ipamConf.RangeEnd, reservelist, ipamConf.OmitRanges, containerID, podRef)

Ip 可用，将 ip 更新到 ippool 里

apiVersion: v1
items:
- apiVersion: whereabouts.cni.cncf.io/v1alpha1
  kind: IPPool
  metadata:
    creationTimestamp: "2023-04-01T09:18:51Z"
    generation: 3
    name: 1.1.1.0-24
    namespace: kube-system
    resourceVersion: "1339436"
    uid: c09f1faf-7c69-4c0d-8b08-9505eb5a6718
  spec:
    allocations:
      "66":
        id: be903950515693036730fc4522f62e5d626846f9f5e3dba5424bc2f3e97b94e5
        podref: default/pod2
      "67":
        id: a2e9650287946248710a9b600f9c410e3f120b948f7d0dec1c5c0feafc2b8e56
        podref: default/pod3
    range: 1.1.1.0/24

创建 OverlappingRangeIPReservation

- apiVersion: whereabouts.cni.cncf.io/v1alpha1
  kind: OverlappingRangeIPReservation
  metadata:
    creationTimestamp: "2023-04-01T10:06:06Z"
    generation: 1
    name: 1.1.1.67
    namespace: kube-system
    resourceVersion: "1339437"
    uid: d0d6ece7-7aea-42a9-a03d-04fc25a8ec1d
  spec:
    containerid: a2e9650287946248710a9b600f9c410e3f120b948f7d0dec1c5c0feafc2b8e56
    podref: default/pod3

根据 cni 规范返回给 cri

Domainset whereabouts

PodInformer watch pod 删除事件，从 IPPool 里删除 pod 分配的 IP
定期 ReconcileIPs
规则

  "reconciler_cron_expression": "30 4 * * *"