【问题标题】:Kubernetes: How to configure hostnetwork pod IP address?Kubernetes:如何配置 hostnetwork pod IP 地址?
【发布时间】:2019-11-26 08:36:35
【问题描述】:

我正在尝试设置 IPv6 kubernetes 集群。我有两个 IPv6 接口和一个 docker 接口(172.17.0.1)。 docker接口由docker自己设置。

kahou@kahou-master:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:50:56:af:1d:25 brd ff:ff:ff:ff:ff:ff
    inet6 2001:420:293:242d:250:56ff:feaf:1d25/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 2591949sec preferred_lft 604749sec
    inet6 fe80::250:56ff:feaf:1d25/64 scope link
       valid_lft forever preferred_lft forever
3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:50:56:af:a5:15 brd ff:ff:ff:ff:ff:ff
    inet6 2000::250:56ff:feaf:a515/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 2591933sec preferred_lft 604733sec
    inet6 2000::3/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:feaf:a515/64 scope link
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:53:f2:46:8c brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
5: tunl0@NONE: <NOARP,UP,LOWER_UP> mtu 1440 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0

当我通过 kubeadm 初始化集群时,所有主机网络 pod IP 都使用 docker IP 地址:

etcd-kahou-master                          1/1     Running             0          177m   172.17.0.1   kahou-master   <none>
kube-apiserver-kahou-master                1/1     Running             0          177m   172.17.0.1   kahou-master   <none>
kube-controller-manager-kahou-master       1/1     Running             0          177m   172.17.0.1   kahou-master   <none>
kube-proxy-pnq7g                           1/1     Running             0          178m   172.17.0.1   kahou-master   <none>
kube-scheduler-kahou-master                1/1     Running             0          177m   172.17.0.1   kahou-master   <none>

是否可以告诉kubeadm我在安装过程中使用的是哪个界面?

下面是我的 api-server 调用(由 kubeadm 生成)

kube-apiserver --authorization-mode=Node,RBAC --bind-address=2001:420:293:242d:250:56ff:feaf:1d25 --service-cluster-ip-range=fd03::/112 --advertise-address=2001:420:293:242d:250:56ff:feaf:1d25 --allow-privileged=true --client-ca-file=/etc/kubernetes/pki/ca.crt --enable-admission-plugins=NodeRestriction --enable-bootstrap-token-auth=true --etcd-cafile=/etc/kubernetes/pki/etcd/ca.crt --etcd-certfile=/etc/kubernetes/pki/apiserver-etcd-client.crt --etcd-keyfile=/etc/kubernetes/pki/apiserver-etcd-client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-client-certificate=/etc/kubernetes/pki/apiserver-kubelet-client.crt --kubelet-client-key=/etc/kubernetes/pki/apiserver-kubelet-client.key --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key --requestheader-allowed-names=front-proxy-client --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-key-file=/etc/kubernetes/pki/sa.pub --tls-cert-file=/etc/kubernetes/pki/apiserver.crt --tls-private-key-file=/etc/kubernetes/pki/apiserver.key

这是我的 kubeadm 配置文件:

apiVersion: kubeadm.k8s.io/v1alpha2
kind: MasterConfiguration
api:
  advertiseAddress: 2001:420:293:242d:250:56ff:feaf:1d25
apiServerExtraArgs:
  bind-address: 2001:420:293:242d:250:56ff:feaf:1d25
  service-cluster-ip-range: fd03::/112
controllerManagerExtraArgs:
  node-cidr-mask-size: "96"
  cluster-cidr: fd02::/80
  service-cluster-ip-range: fd03::/112
networking:
  serviceSubnet: fd03::/112
nodeRegistration:
  node-ip: 2001:420:293:242d:250:56ff:feaf:1d25

【问题讨论】:

    标签: kubernetes kubeadm


    【解决方案1】:

    关于配置 node-ip 以通过 kubeadm 配置文件传递给 kubelet 的有用说明: 根据https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta1 和一些实验,它应该在nodeRegistration 部分的kubeletExtraArgs 下(使用配置文件中的IP 示例):

    apiVersion: kubeadm.k8s.io/v1beta2
    kind: InitConfiguration
    nodeRegistration:
      kubeletExtraArgs:
        node-ip: 2001:420:293:242d:250:56ff:feaf:1d25
    

    【讨论】:

      【解决方案2】:

      您可以使用 kubeadm config 配置此行为。您是否尝试过使用--pod-network-cidr string。更多详情见官方文档https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-config/

      【讨论】:

      • pod-network-cidr 仅适用于非 hostnetwork pod。我正在寻找 hostnetwork pod IP。
      • 对不起,我错过了,这实际上很奇怪,你的 kube-api 清单是什么样的。你能补充一下这些细节吗?
      • 在问题中添加了更多详细信息。谢谢。
      • 目前配置看起来不错,你可以添加ps aux | grep kubelet 输出。我想看看kubelet配置有没有问题。
      猜你喜欢
      • 1970-01-01
      • 2019-12-07
      • 2017-05-24
      • 1970-01-01
      • 2019-09-16
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多