初始化Kubernetes集群

Question

我正在尝试在ubuntu 18.04系统上安装Kubernetes集群..

作为使用以下命令初始化集群的一部分，得到以下错误

        [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.14.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.14.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.14.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.14.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.1: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.3.10: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1
        [ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.3.1: output: Error response from daemon: Get https://k8s.gcr.io/v2/: remote error: tls: access denied
, error: exit status 1

当我尝试运行wget https://k8s.gcr.io/v2/时，出现以下错误：

Proxy request sent, awaiting response... 401 Unauthorized
Username/Password Authentication Failed.

你能让我知道是什么问题吗？

Answer 1

就我而言

[root@instance-1 ~]# wget https://k8s.gcr.io/v2/
--2019-08-26 12:58:24--  https://k8s.gcr.io/v2/
Resolving k8s.gcr.io (k8s.gcr.io)... 64.233.167.82, 2a00:1450:400c:c06::52
Connecting to k8s.gcr.io (k8s.gcr.io)|64.233.167.82|:443... connected.
HTTP request sent, awaiting response... 401 Unauthorized
Authorization failed.

那可能是代理问题。 检查[Kubeadm]无法提取图像 ，并且更具体[此答案]（ https://github.com/kubernetes/kubeadm/issues/1201#issuecomment-494686022 。

因此，尝试将您的泊坞窗配置为使用代理 ，希望您的问题能够得到解决。

下面总结了这两种方法的命令集：

方法1：在/ etc / sysconfig / docker文件中配置代理变量

-在/ etc / sysconfig / docker文件中添加以下配置

# cat /etc/sysconfig/docker
HTTP_PROXY="http://USERNAME:PASSWORD@[your.proxy.server]:[port]"
HTTPS_PROXY="https://USERNAME:PASSWORD@[your.proxy.server]:[port]

-重新启动docker

# service docker restart

方法2：

1）创建一个插件

# mkdir /etc/systemd/system/docker.service.d

2）创建一个名称为/etc/systemd/system/docker.service.d/http-proxy.conf的文件，该文件添加HTTP_PROXY环境变量：

[Service]
Environment="HTTP_PROXY=http://user01:password@10.10.10.10:8080/"
Environment="HTTPS_PROXY=https://user01:password@10.10.10.10:8080/"
Environment="NO_PROXY= hostname.example.com,172.10.10.10"

3）重新加载systemd守护程序

# systemctl daemon-reload

4）重启docker

# systemctl restart dock docker 5）验证是否已加载配置：

# systemctl show docker --property Environment
Environment=GOTRACEBACK=crash HTTP_PROXY=http://10.10.10.10:8080/ HTTPS_PROXY=http://10.10.10.10:8080/ NO_PROXY= hostname.example.com,172.10.10.10