Question

来自http://kubernetes.io/docs/getting-started-guides/kubeadm/

CentOS Linux版本7.2.1511（核心）

（1/4）在主机上安装kubelet和kubeadm ..... 没关系

$sudo docker -v

Docker version 1.10.3, build cb079f6-unsupported
$sudo kubeadm version
$kubeadm version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.0-alpha.0.1534+cf7301f16c0363-dirty", GitCommit:"cf7301f16c036363c4fdcb5d4d0c867720214598", GitTreeState:"dirty", BuildDate:"2016-09-27T18:10:39Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
$sudo systemctl enable docker && systemctl start docker
$sudo systemctl enable kubelet && systemctl start kubelet

再次好了

$ sudo kubeadm init

<master/tokens> generated token: "15a340.9910f948879b5d99"
<master/pki> created keys and certificates in "/etc/kubernetes/pki"
<util/kubeconfig> created "/etc/kubernetes/kubelet.conf"
<util/kubeconfig> created "/etc/kubernetes/admin.conf"
<master/apiclient> created API client configuration
<master/apiclient> created API client, waiting for the control plane to become ready

在那个地方，进程停了下来。可能，我不能理解某些东西，但RedHat OpenShift版本3使用kubernetes + docker。我试过OpenShift v3 docker版本下载 - 没关系。

Answer 1

我通过在/ etc / hosts文件中将私有IP地址声明为localhost来修复该问题。示例：/ etc / hosts

10.0.0.2  localhost

然后我遇到kubectl让节点抛出的问题：

The connection to the server localhost:8080 was refused - did you specify the right host or port?

我通过将生成的conf复制到本地kube配置来修复。

cp /etc/kubernetes/kubelet.conf ~/.kube/config

Answer 2

这里有几种可能性 - ：

1）在较旧的kubeadm版本中，selinux此时阻止访问

2）如果您在代理服务器后面，则需要将常用内容添加到kubeadm环境中 - ：

HTTP_PROXY
HTTPS_PROXY
NO_PROXY

另外，我在任何地方都没有记录 - ：

KUBERNETES_HTTP_PROXY 
KUBERNETES_HTTPS_PROXY
KUBERNETES_NO_PROXY

Answer 3

 .....
<master/apiclient> all control plane components are healthy after 20.585964   seconds
<master/apiclient> waiting for at least one node to register and become ready
<master/apiclient> first node is ready after 8.259447 seconds
<master/apiclient> attempting a test deployment
<master/apiclient> test deployment succeeded
<master/discovery> created essential addon: kube-discovery, waiting for it   to become ready
<master/discovery> kube-discovery is ready after 66.415198 seconds

kubeadm: I am an alpha version, my authors welcome your feedback and bug reports
kubeadm: please create an issue using      https://github.com/kubernetes/kubernetes/issues/new
kubeadm: and make sure to mention @kubernetes/sig-cluster-lifecycle. Thank you!

无法创建基本的kube-proxy插件[超时：请求未在允许的持续时间内完成]

固定。但是我成功地安装并配置了1.2.0版本......哦

Kubernetes配置步骤2 CentOS 7

3 个答案: