Kubernetes的配置步驟2的CentOS 7

從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版本下載 - 沒問題。

來源

2016-10-10 zirf

Kubernetes [issue 34695] CentOS 7（https://github.com/kubernetes/kubernetes/issues/34695）。州是「開放」的。 Kubernetes [問題33729] Ubuntu 16（https://github.com/kubernetes/kubernetes/issues/33729）狀態爲「打開」。 – zirf

我通過在/ 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

來源

2016-10-16 17:17:41 Jeff

完成，但沒有更改。上面我添加了兩個來自github/kubernetes的問題。目前沒有明確的解決方案，只是解決方法。 – zirf

有一對夫婦的可能性在這裏 - ：

1）在舊kubeadm版本的SELinux塊在這一點上

2）如果您是使用代理，你將需要添加的訪問通常在kubeadm環境 - ：

HTTP_PROXY 
HTTPS_PROXY 
NO_PROXY

另外，我還沒有看到任何相關文檔 - ：

KUBERNETES_HTTP_PROXY 
KUBERNETES_HTTPS_PROXY 
KUBERNETES_NO_PROXY

來源

2016-11-01 22:57:31 msduk

..... 
<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.2.0版本...噢

來源

2016-11-13 11:51:36 zirf

Kubernetes的配置步驟2的CentOS 7

回答

相關問題