域名已经成功解析到master 这个主机的IP

Choerodon Installation management
#1

  • Choerodon平台版本: 0.17.0

  • 遇到问题的执行步骤:

执行一键安装， 已经把域名配置到了集群中来 指向的是master 的公网IP； mysql postsql redis 已经安装成功 在执行gitlab 的时候 报 域名未解析到集群； （已经解决到进群 并且在主机 和容器ping 都通了）

  • 文档地址:

  • 环境信息(如:节点信息):

[root@rke c7nctl-0.16.1]# kubectl get pod -n c7n-system -o wide
NAME                      READY     STATUS    RESTARTS   AGE       IP           NODE
c7n-slaver-gxgnd          1/1       Running   0          42m       10.42.1.10   node02
c7n-slaver-kbpj4          1/1       Running   0          42m       10.42.2.35   node01
mysql-7cb878b658-xwk5m    1/1       Running   0          42m       10.42.2.36   node01
postgresql-postgresql-0   1/1       Running   0          42m       10.42.1.11   node02
redis-7d6cd7c487-b5rnr    1/1       Running   0          42m       10.42.1.12   node02



root@rke c7nctl-0.16.1]# kubectl get node
NAME      STATUS    ROLES               AGE       VERSION
node01    Ready     worker              23h       v1.11.1
node02    Ready     worker              23h       v1.11.1
rke       Ready     controlplane,etcd   23h       v1.11.1


# docker info

[root@rke c7nctl-0.16.1]# docker info
Containers: 22
 Running: 9
 Paused: 0
 Stopped: 13
Images: 8
Server Version: 17.03.2-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
  • 报错日志:
[root@rke c7nctl-0.16.1]# ./c7nctl install -c config.yml --no-timeout --version=0.17
2019/06/14 11:03:24 [INFO] getting resource /version.yml
2019/06/14 11:03:24 [INFO] getting resource /0.17/install.yml
2019/06/14 11:03:24 [INFO] namespace c7n-system already exists
2019/06/14 11:03:25 [INFO] waiting slaver running...
2019/06/14 11:03:26 [INFO] waiting slaver running...
2019/06/14 11:03:26 [INFO] clean history jobs...
2019/06/14 11:03:26 [INFO] start install postgresql
2019/06/14 11:03:26 [INFO] using exist release postgresql
2019/06/14 11:03:26 [INFO] start install mysql
2019/06/14 11:03:26 [INFO] using exist release mysql
2019/06/14 11:03:26 [INFO] start install redis
2019/06/14 11:03:26 [INFO] using exist release redis
2019/06/14 11:03:26 [INFO] start install gitlab
2019/06/14 11:03:27 [INFO] Waiting postgresql running
2019/06/14 11:03:27 [INFO] Waiting redis running
2019/06/14 11:03:27 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:29 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:31 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:33 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:35 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:37 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:39 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:41 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:43 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:45 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:47 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:49 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:51 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:53 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:55 [INFO] Wait domain gitlab.paas.03in.com point to cluster, check acme want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}, retry
2019/06/14 11:03:57 [Error] 请检查您的域名: gitlab.paas.xxxx.com 已正确解析到集群
2019/06/14 11:03:57 [Error] install failed
Error: Check domain failed want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}
Usage:
  c7nctl install [flags]

Flags:
  -c, --config-file string     User Config file to read from, User define config by this file
      --debug                  enable debug output
  -h, --help                   help for install
      --no-timeout             disable install job timeout
      --prefix string          add prefix to all helm release
  -r, --resource-file string   Resource file to read from, It provide which app should be installed
      --skip-input             use default username and password to avoid user input
      --version string         specify a version

Global Flags:
      --config string    config file (default is $HOME/.c7n.yaml)
  -o, --orgCode string   org code
  -p, --proCode string   pro code

Check domain failed want yLet282G66bgg2b1xSN7D1PoJg got {"success":false}
  • 原因分析:

    提出您分析问题的过程,以便我们能更准确的找到问题所在

gitlab 目前在pod 中未有pod 在运行 说明 gitlab 还未安装

  • 疑问:

    提出您对于遇到和解决该问题时的疑问

域名解析已经成功后 为啥还提醒未解析
#2

如果你使用rancher，请按照rancher的文档进行域名和网络的相关配置。

#4

再请教一下 填写域名的那个配置文件 中的域名能加上端口吗？ 情况特殊不能用80端口。 我测试加上了其他端口 运行后报DNS错。

#5

你好楼主，问题解决了吗？我安装0.19版本也是遇到同样的问题

#6

我通过自己 搭建DNS 解决了。 在局域网内搭建一个域名解析系统。 在k8s 内部指定 dns 通过自定义域名解决；

apiVersion: v1
kind: ConfigMap
metadata:
    name: kube-dns
    namespace: kube-system
    labels:
        addonmanager.kubernetes.io/mode: EnsureExists
data:
    tubDomains: |
       {"ls.com":["192.168.1.174"]}
    upstreamNameservers: |
        ["223.5.5.5", "192.168.1.174"]

kubectl create -f kube-dns.yaml