Не могу получить доступ к порту KubeAPI в kubernetes + ранчер

Question

Не могу получить доступ к порту KubeAPI в kubernetes + ранчер

У меня есть следующая конфигурация для запуска. когда я до rke, Я получаю ошибку.

фермер-cluster.yml

nodes:
  - address: 192.168.88.246
    internal_address: 172.17.0.1
    user: dockeruser
    role: [controlplane,worker,etcd]
  - address: 192.168.88.243
    internal_address: 172.17.0.1
    user: dockeruser
    role: [controlplane,worker,etcd]
  - address: 192.168.88.245
    internal_address: 172.17.0.1
    user: dockeruser
    role: [controlplane,worker,etcd]

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

когда я до rke я получаю следующую ошибку

FATA[0059] [network] Can't access KubeAPI port [6443] on Control Plane host: 192.168.88.245

журнал данных

[root@localhost ~]# rke up --config ./rancher-cluster.yml
INFO[0000] Building Kubernetes cluster
INFO[0000] [dialer] Setup tunnel for host [192.168.88.243]
INFO[0000] [dialer] Setup tunnel for host [192.168.88.245]
INFO[0000] [dialer] Setup tunnel for host [192.168.88.246]
INFO[0001] [state] Found local kube config file, trying to get state from cluster
INFO[0001] [reconcile] Local config is not valid, rebuilding admin config
INFO[0001] [reconcile] Rebuilding and updating local kube config
INFO[0001] Successfully Deployed local admin kubeconfig at [./kube_config_rancher-cluster.yml]
INFO[0014] Successfully Deployed local admin kubeconfig at [./kube_config_rancher-cluster.yml]
INFO[0026] Successfully Deployed local admin kubeconfig at [./kube_config_rancher-cluster.yml]
INFO[0026] [state] Fetching cluster state from Kubernetes
INFO[0056] Timed out waiting for kubernetes cluster to get state
INFO[0056] [state] Fetching cluster state from Nodes
INFO[0057] [network] Deploying port listener containers
INFO[0058] [network] Successfully started [rke-etcd-port-listener] container on host [192.168.88.246]
INFO[0058] [network] Successfully started [rke-etcd-port-listener] container on host [192.168.88.243]
INFO[0058] [network] Successfully started [rke-etcd-port-listener] container on host [192.168.88.245]
INFO[0059] [network] Successfully started [rke-worker-port-listener] container on host [192.168.88.243]
INFO[0059] [network] Successfully started [rke-worker-port-listener] container on host [192.168.88.246]
INFO[0059] [network] Successfully started [rke-worker-port-listener] container on host [192.168.88.245]
INFO[0059] [network] Port listener containers deployed successfully
INFO[0059] [network] Running etcd <-> etcd port checks
INFO[0060] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0060] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0060] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0060] [network] Running control plane -> etcd port checks
INFO[0061] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0061] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0061] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0061] [network] Running control plane -> worker port checks
INFO[0061] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0061] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0061] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0061] [network] Running workers -> control plane port checks
INFO[0062] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0062] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0062] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0062] [network] Checking KubeAPI port Control Plane hosts
FATA[0062] [network] Can't access KubeAPI port [6443] on Control Plane host: 192.168.88.245
[root@localhost ~]# rke up --config ./rancher-cluster.yml
INFO[0000] Building Kubernetes cluster
INFO[0000] [dialer] Setup tunnel for host [192.168.88.246]
INFO[0000] [dialer] Setup tunnel for host [192.168.88.243]
INFO[0001] [dialer] Setup tunnel for host [192.168.88.245]
INFO[0001] [state] Found local kube config file, trying to get state from cluster
INFO[0001] [reconcile] Local config is not valid, rebuilding admin config
INFO[0001] [reconcile] Rebuilding and updating local kube config
INFO[0001] Successfully Deployed local admin kubeconfig at [./kube_config_rancher-cluster.yml]
INFO[0011] Successfully Deployed local admin kubeconfig at [./kube_config_rancher-cluster.yml]
INFO[0023] Successfully Deployed local admin kubeconfig at [./kube_config_rancher-cluster.yml]
INFO[0023] [state] Fetching cluster state from Kubernetes
INFO[0053] Timed out waiting for kubernetes cluster to get state
INFO[0053] [state] Fetching cluster state from Nodes
INFO[0054] [network] Deploying port listener containers
INFO[0055] [network] Successfully started [rke-etcd-port-listener] container on host [192.168.88.245]
INFO[0055] [network] Successfully started [rke-cp-port-listener] container on host [192.168.88.243]
INFO[0056] [network] Successfully started [rke-worker-port-listener] container on host [192.168.88.245]
INFO[0056] [network] Port listener containers deployed successfully
INFO[0056] [network] Running etcd <-> etcd port checks
INFO[0056] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0056] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0056] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0057] [network] Running control plane -> etcd port checks
INFO[0057] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0057] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0057] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0057] [network] Running control plane -> worker port checks
INFO[0058] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0058] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0058] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0058] [network] Running workers -> control plane port checks
INFO[0058] [network] Successfully started [rke-port-checker] container on host [192.168.88.246]
INFO[0058] [network] Successfully started [rke-port-checker] container on host [192.168.88.245]
INFO[0059] [network] Successfully started [rke-port-checker] container on host [192.168.88.243]
INFO[0059] [network] Checking KubeAPI port Control Plane hosts
FATA[0059] [network] Can't access KubeAPI port [6443] on Control Plane host: 192.168.88.245

В 192.168.88.24 (узел), kube-apiserver уже бежит.

Я уже открываю порт

firewall-cmd --zone=public --add-port=6443/tcp --permanent
firewall-cmd --reload

2

docker kubernetes kubectl rancher rke

Источник

user1573835 04 фев '19 в 09:41

0 ответов

Другие вопросы по тегам docker kubernetes kubectl rancher rke

user8412333 09 авг '20 в 10:29 2020-08-09 10:29 · Answer 1 · 2020-08-09 10:29

Проблема в том, что все IP-адреса internal_address одинаковы. Этот параметр используется для задания IP-адреса, по которому узлы должны обмениваться данными для соединений между узлами. Обычно мы видим этот вариант, когда ваши серверы находятся за NAT.

Пожалуйста, попробуйте следующий cluster.yml

nodes:
  - address: 192.168.88.246
    internal_address: 192.168.88.246
    user: dockeruser
    role: [controlplane,worker,etcd]
  - address: 192.168.88.243
    internal_address: 192.168.88.243
    user: dockeruser
    role: [controlplane,worker,etcd]
  - address: 192.168.88.245
    internal_address: 192.168.88.245
    user: dockeruser
    role: [controlplane,worker,etcd]

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

user11416679 28 апр '19 в 09:34 2019-04-28 09:34 · Answer 2 · 2019-04-28 09:34

У вас все еще есть проблема... Рекомендую в случае необходимости отправиться на слабый канал Rancher... http://slack.rancher.io/

0

Источник

user11416679 28 апр '19 в 09:34