在Rancher / Kubernates(RKE)中为internal_address打开端口吗?

时间:2019-02-01 03:37:52

标签: docker kubernetes rancher rke

我具有以下配置,可以使用Rancher (RKE)设置集群。

rancher-config.yml

nodes:
  - address: 192.168.88.204
    internal_address: 172.16.22.12
    user: dockeruser
    role: [controlplane,worker,etcd]
  - address: 192.168.88.203
    internal_address: 172.16.32.37
    user: dockeruser
    role: [controlplane,worker,etcd]
  - address: 192.168.88.202
    internal_address: 172.16.42.73
    user: dockeruser
    role: [controlplane,worker,etcd]

services:
  etcd:
    snapshot: true
    creation: 6h
    retention: 24h 

根据Rancher Networking,我已经为所有节点(192.168.88.204、192.168.88.203、192.168.88.202)打开了以下端口,作为防火墙服务。

node-firewall.xml

<?xml version="1.0" encoding="utf-8"?>
<service>
    <port port="2376" protocol="tcp"/>
    <port port="2379" protocol="tcp"/>
    <port port="2380" protocol="tcp"/>
    <port port="8472" protocol="udp"/>
    <port port="9099" protocol="tcp"/>
    <port port="10250" protocol="tcp"/>
    <port port="443" protocol="tcp"/>
    <port port="6443" protocol="tcp"/>
    <port port="8472" protocol="udp"/>
    <port port="6443" protocol="tcp"/>
    <port port="10254" protocol="tcp"/>
    <port port="30000-32767" protocol="tcp"/>
</service>

-> commmend

firewall-offline-cmd --new-service-from-file=node-firewall.xml --name=node-firewall
firewall-cmd --reload
firewall-cmd --add-service node-firewall

我的RKE安装在192.168.88.151上。对于RKE->

rancher-firewall.xml

<?xml version="1.0" encoding="utf-8"?>
<service>
    <port port="80" protocol="tcp"/>
    <port port="433" protocol="tcp"/>
    <port port="22" protocol="tcp"/>
    <port port="2376" protocol="tcp"/>
    <port port="6443" protocol="tcp"/>
</service>
firewall-offline-cmd --new-service-from-file=rancher-firewall.xml --name=rancher-firewall
firewall-cmd --reload
firewall-cmd --add-service rancher-firewall

因此,我运行以下命令来提高我的RKE

rke up --config ./rancher-config.yml

日志是

[root@localhost ~]# rke up --config ./rancher-config.yml
INFO[0000] Building Kubernetes cluster
INFO[0000] [dialer] Setup tunnel for host [192.168.88.204]
INFO[0000] [dialer] Setup tunnel for host [192.168.88.203]
INFO[0000] [dialer] Setup tunnel for host [192.168.88.202]
INFO[0001] [network] Deploying port listener containers
INFO[0001] [network] Port listener containers deployed successfully
INFO[0001] [network] Running etcd <-> etcd port checks
INFO[0001] [network] Successfully started [rke-port-checker] container on host [192.168.88.202]
INFO[0001] [network] Successfully started [rke-port-checker] container on host [192.168.88.204]
INFO[0001] [network] Successfully started [rke-port-checker] container on host [192.168.88.203]
FATA[0016] [network] Host [192.168.88.202] is not able to connect to the following ports: 
            [172.16.22.12:2379, 172.16.22.12:2380, 172.16.32.37:2379, 172.16.32.37:2380, 172.16.42.73:2380, 172.16.42.73:2379]. 
            Please check network policies and firewall rules

我的问题是如何为internal_address群集中的所有节点打开kubernates的端口?

2 个答案:

答案 0 :(得分:1)

可能是缺乏我的经验。我只是分享我发现的东西。 internal_address必须是docker的(网关)的IP地址。 知道每个节点的docker的IP地址(192.168.88.204、192.168.88.203、192.168.88.202)。

运行推荐的docker network ls。您可能会得到以下网络信息。

NETWORK ID          NAME                DRIVER              SCOPE
aa13d08f2676        bridge              bridge              local
02eabe818790        host                host                local
1e5bb430d790        none                null                local

并运行命令docker network inspect bridge以获取bridge的ip地址。 您将获得以下类似信息。

[
    {
        "Name": "bridge",
        "Id": "aa13d08f2676e40df5a82521fccc4e402ef6b04f82bcd414cd065a1859b3799d",
        "Created": "2019-01-31T21:32:02.381082005-05:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.17.0.0/16",
                    "Gateway": "172.17.0.1"
                }
            ]
        },
        ....
        ...
        ..
        .

]

并按如下所示配置rancher-config.yml并再次运行rke up --config ./rancher-config.yml

nodes:
  - address: 192.168.88.204
    internal_address: 172.17.0.1
    ...
...
..
..

答案 1 :(得分:0)

那是不正确的。

  

internal_address提供了具有   具有多个地址的节点设置特定的地址以用于   专用网络上的主机间通信。如果内部地址   未设置,该地址用于主机间通信。

https://rancher.com/docs/rke/v0.1.x/en/config-options/nodes/#internal-address

您可能有防火墙问题。

检查您的活动区域以及这些区域中的接口。

firewall-cmd --get-active-zones