2016-10-10 39 views
0

http://kubernetes.io/docs/getting-started-guides/kubeadm/Kubernetes的配置步骤2的CentOS 7

的CentOS Linux的发布1511年2月7日(核心)

(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 

并在那个地方proccess停止。 大概,我不能理解一些东西,但是RedHat OpenShift版本3使用kubernetes + docker。我尝试了OpenShift v3 docker版本下载 - 没问题。

+0

Kubernetes [issue 34695] CentOS 7(https://github.com/kubernetes/kubernetes/issues/34695)。州是“开放”的。 Kubernetes [问题33729] Ubuntu 16(https://github.com/kubernetes/kubernetes/issues/33729)状态为“打开”。 – zirf

回答

0

我通过在/ etc/hosts文件中声明私有IP地址为localhost来解决该问题。 实施例中:/ etc /主机

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 
+0

完成,但没有更改。上面我添加了两个来自github/kubernetes的问题。目前没有明确的解决方案,只是解决方法。 – zirf

0

有一对夫妇的可能性在这里 - :

1)在旧kubeadm版本的SELinux块在这一点上

2)如果您是使用代理,你将需要添加的访问通常在kubeadm环境 - :

HTTP_PROXY 
HTTPS_PROXY 
NO_PROXY 

另外,我还没有看到任何相关文档 - :

KUBERNETES_HTTP_PROXY 
KUBERNETES_HTTPS_PROXY 
KUBERNETES_NO_PROXY 
0
..... 
<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-代理插件[超时:请求没有允许时间内完成]

  1. 固定。但我成功安装并配置了1.2.0版本...噢