添加链接
link之家
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接

环境说明(centos7.2):

192.168.111.117 master
192.168.111.123 slave1
192.168.111.184 slave2

配置互信

生成ssh 密钥对
[root@master




    
 ~]# ssh-keygen
把本地的ssh公钥文件安装到远程主机对应的账户
[root@master ~]# ssh-copy-id master
[root@master ~]# ssh-copy-id slave1
[root@master ~]# ssh-copy-id slave2

关闭防火墙&&关闭selinux

[root@master ~]# systemctl stop firewalld
[root@master ~]# systemctl disable firewalld
[root@master ~]# cat /etc/selinux/config 
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected. 
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

开始安装

所有节点操作

下载链接: https://pan.baidu.com/s/1c2O1gIW 密码: 9s92

比对md5解压离线包

MD5 (k8s_images.tar.bz2) = b60ad6a638eda472b8ddcfa9006315ee

下载相关rpm 包还有相关 docker images. 并解压

[root@master ~]# tar xvf k8s_images.tar.gz2

安装docker-ce

[root@master ~]# cd k8s_images/ 
[root@master k8s_images]# yum -y localinstall docker-ce-selinux-17.03.2.ce-1.el7.centos.noarch.rpm docker-ce-17.03.2.ce-1.el7.centos.x86_64.rpm 

修改docker的镜像源为国内的daocloud(或者阿里云的都行)。

curl -sSL https://get.daocloud.io/daotools/set_mirror.sh | sh -s http://a58c8480.m.daocloud.io

启动docker,并设置开机启动

[root@master ~]# systemctl start docker;systemctl enable docker

配置系统路由参数,防止kubeadm报路由警告

[root@master ~]# echo "
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1vm.swappiness = 0" >> /etc/sysctl.conf[root@master ~]# sysctl -p
[root@master ~]# swapoff -a && sed -i '/swap/d' /etc/fstab     #一定要删除swap,否则集群初始化不了(把/etc/fstab文件中swap那行也删掉,不然重启后又重新挂载了)

安装kubadm kubelet kubectl

[root@master k8s_images]# yum -y localinstall kubectl-1.9.0-0.x86_64.rpm \kubeadm-1.9.0-0.x86_64.rpm kubelet-1.9.9-9.x86_64.rpm  \kubernetes-cni-0.6.0-0.x86_64.rpm socat-1.7.3.2-2.el7.x86_64.rpm 

加载镜像

[root@master k8s_images]# cd docker_images/
[root@master docker_images]# ll
total 999696
-rw-r--r-- 1 root root 192984064 Dec 26 11:32 etcd-amd64_v3.1.10.tar
-rw-r--r-- 1 root root  52185600 Dec 27 20:36 flannel:v0.9.1-amd64.tar
-rw-r--r-- 1 root root  41241088 Dec 27 20:34 k8s-dns-dnsmasq-nanny-amd64_v1.14.7.tar
-rw-r--r-- 1 root root  50545152 Dec 27 23:02 k8s-dns-kube-dns-amd64_1.14.7.tar
-rw-r--r-- 1 root root  42302976 Dec 27 22:59 k8s-dns-sidecar-amd64_1.14.7.tar
-rw-r--r-- 1 root root 210598400 Dec 26 11:28 kube-apiserver-amd64_v1.9.0.tar
-rw-r--r-- 1 root root 137975296 Dec 26 11:30 kube-controller-manager-amd64_v1.9.0.tar
-rw-r--r-- 1 root root 110955520 Dec 29 13:13 kube-proxy-amd64_v1.9.0.tar
-rw-r--r-- 1 root root 121195008 Jan  1 20:24 kubernetes-dashboard_v1.8.1.tar
-rw-r--r-- 1 root root  62920704 Dec 26 11:30 kube-scheduler-amd64_v1.9.0.tar
-rw-r--r-- 1 root root    765440 Dec 27 20:32 pause-amd64_3.0.tar
[root@master docker_images]# for image in `ls -l . | awk '{print $9}'`; \do echo "$image is loading" && docker load < ${image};done

master 节点操作

#启动kubelet(这时候查看/var/log/messages日志,会发现有报错)
[root@master ~]# systemctl start kubelet && systemctl enable kubelet

开始初始化master节点

kubernetes 默认支持多重网络插件如flannel、weave、calico,这里使用flannel,就必须设置–pod-network-cidr 参数,

[root@master ~]# kubeadm init --kubernetes-version=v1.9.0 --pod-network-cidr=10.224.0.0/16 --token-ttl=0

参数说明

Jan 20 15:22:53 huaicong-1 kubelet: E0120 15:22:53.551735   24627 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.111.117:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dhuaicong-1.novalocal&limit=500&resourceVersion=0: dial tcp 192.168.111.117:6443: getsockopt: connection refused
Jan 20 15:22:53 huaicong-1 kubelet: E0120 15:22:53.551845   24627 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://192.168.111.117:6443/api/v1/nodes?fieldSelector=metadata.name%3Dhuaicong-1.novalocal&limit=500&resourceVersion=0: dial tcp 192.168.111.117:6443: getsockopt: connection refused
Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.557159   24627 kubelet_network.go:139] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth"
Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.557178   24627 kubelet.go:571] Hairpin mode set to "hairpin-veth"
Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.557212   24627 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.557240   24627 client.go:80] Connecting to docker on unix:///var/run/docker.sock
Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.557249   24627 client.go:109] Start docker client with request timeout=2m0s
Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.559152   24627 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.581459   24627 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.581544   24627 docker_service.go:232] Docker cri networking managed by cni
Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.599739   24627 docker_service.go:237] Docker Info: &{ID:FMCL:A6AR:LAHK:SS2I:2SJI:ZY73:HYS4:DRRU:AJI4:JOQM:L5XK:ZGLK Containers:0 ContainersRunning:0 ContainersPaused:0 ContainersStopped:0 Images:11 Driver:overlay DriverStatus:[[Backing Filesystem xfs] [Supports d_type true]] SystemStatus:[] Plugins:{Volume:[local] Network:[bridge host macvlan null overlay] Authorization:[] Log:[]} MemoryLimit:true SwapLimit:true KernelMemory:true CPUCfsPeriod:true CPUCfsQuota:true CPUShares:true CPUSet:true IPv4Forwarding:true BridgeNfIptables:true BridgeNfIP6tables:true Debug:false NFd:16 OomKillDisable:true NGoroutines:22 SystemTime:2018-01-20T15:22:53.586684761+08:00 LoggingDriver:json-file CgroupDriver:cgroupfs NEventsListener:0 KernelVersion:3.10.0-514.el7.x86_64 OperatingSystem:CentOS Linux 7 (Core) OSType:linux Architecture:x86_64 IndexServerAddress:https://index.docker.io/v1/ RegistryConfig:0xc420e63960 NCPU:




    
2 MemTotal:3975086080 GenericResources:[] DockerRootDir:/var/lib/docker HTTPProxy: HTTPSProxy: NoProxy: Name:huaicong-1.novalocal Labels:[] ExperimentalBuild:false ServerVersion:17.03.2-ce ClusterStore: ClusterAdvertise: Runtimes:map[runc:{Path:docker-runc Args:[]}] DefaultRuntime:runc Swarm:{NodeID: NodeAddr: LocalNodeState:inactive ControlAvailable:false Error: RemoteManagers:[] Nodes:0 Managers:0 Cluster:0xc4201cb400} LiveRestoreEnabled:false Isolation: InitBinary:docker-init ContainerdCommit:{ID:4ab9917febca54791c5f071a9d1f404867857fcc Expected:4ab9917febca54791c5f071a9d1f404867857fcc} RuncCommit:{ID:54296cf40ad8143b62dbcaa1d90e520a2136ddfe Expected:54296cf40ad8143b62dbcaa1d90e520a2136ddfe} InitCommit:{ID:949e6fa Expected:949e6fa} SecurityOptions:[name=seccomp,profile=default]}
Jan 20 15:22:53 huaicong-1 kubelet: error: failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: "systemd" is different from docker cgroup driver: "cgroupfs"
Jan 20 15:22:53 huaicong-1 systemd: kubelet.service: main process exited, code=exited, status=1/FAILURE
Jan 20 15:22:53 huaicong-1 systemd: Unit kubelet.service entered failed state.
Jan 20 15:22:53 huaicong-1 systemd: kubelet.service failed.

查看日志发现启动不了

原来是kubelet 的cgroup dirver 与 docker的不一样。docker默认使用cgroupfs( 可以用docker info | grep cgroup查看当前docker驱动方式 ),keubelet 默认使用systemd。

[root@master ~]# vim /etc/systemd/system/kubelet.service.d/10-kubeadm.conf 
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true"
Environment="KUBELET_NETWORK_ARGS=--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin"
Environment="KUBELET_DNS_ARGS=--cluster-dns=10.96.0.10 --cluster-domain=cluster.local"
Environment="KUBELET_AUTHZ_ARGS=--authorization-mode=Webhook --client-ca-file=/etc/kubernetes/pki/ca.crt"
Environment="KUBELET_CADVISOR_ARGS=--cadvisor-port=0"
Environment="KUBELET_CGROUP_ARGS=--cgroup-driver=cgroupfs"
Environment="KUBELET_CERTIFICATE_ARGS=--rotate-certificates=true --cert-dir=/var/lib/kubelet/pki"
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_SYSTEM_PODS_ARGS $KUBELET_NETWORK_ARGS $KUBELET_DNS_ARGS $KUBELET_AUTHZ_ARGS $KUBELET_CADVISOR_ARGS $KUBELET_CGROUP_ARGS $KUBELET_CERTIFICATE_ARGS $KUBELET_EXTRA_ARGS

systemctl daemon-reload && systemctl restart kubelet

&& systemctl enable kubelet

[root@master ~]# kubeadm  init --kubernetes-version=v1.9.0 --pod-network-cidr=10.244.0.0/16 
[init] Using Kubernetes version: v1.9.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
    [WARNING Hostname]: hostname "huaicong-1.novalocal" could not be reached
    [WARNING Hostname]: hostname "huaicong-1.novalocal" lookup huaicong-1.novalocal on 8.8.4.4:53: no such host
    [WARNING FileExisting-crictl]: crictl not found in system path
[preflight] Starting the kubelet service
[certificates] Generated ca certificate and key.
[certificates] Generated apiserver certificate and key.
[certificates] apiserver serving cert is signed for DNS names [huaicong-1.novalocal kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.111.117]
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] Generated sa key and public key.
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk: "admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf"
[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".
[init] This might take a minute or longer if the control plane images have to be pulled.
[apiclient] All control plane components are healthy after 30.001793 seconds
[uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[markmaster] Will mark node huaicong-1.novalocal as master by adding a label and a taint
[markmaster] Master huaicong-1.novalocal tainted and labelled with key/value: node-role.kubernetes.io/master=""
[bootstraptoken] Using token: 7529d9.235a9be16773cad7
[bootstraptoken] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstraptoken] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstraptoken] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstraptoken] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: kube-dns
[addons] Applied essential addon: kube-proxy
Your Kubernetes master has initialized successfully!
To start using your cluster, you need to run the following as a regular user:
  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config
You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/
You can now join any number of machines by running the following on each node
as root:
  kubeadm join --token 7529d9.235a9be16773cad7 192.168.111.117:6443 --discovery-token-ca-cert-hash sha256:5cde22b6b719d1af19c711b87016163baafd38e5588786ebd4a2b975a07439fd

kubeadm join xxxx 要保留下来(当前版本无法回显,以后要添加找不到就尴尬了)

如果忘记了,可以通过kubeadm token list 获取(但这个不全,无法用来添加新节点)

[root@master k8s_images]# kubeadm token list
TOKEN                     TTL       EXPIRES                     USAGES                   DESCRIPTION                                                EXTRA GROUPS
7529d9.235a9be16773cad7   21h       2018-01-21T16:00:46+08:00   authentication,signing   The default bootstrap token generated by 'kubeadm init'.   system:bootstrappers




    
:kubeadm:default-node-token

###由于安全原因,默认情况下pod不会被schedule到master节点上,可以通过下面命令解除这种限制:

kubectl taint nodes --all node-role.kubernetes.io/master-

按照上面提示,此时还不能用kubectl 控制集群。需要配置环境变量

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

查看kubectl版本信息

[root@master k8s_images]# kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

安装网络,可用使用flannel、macvlan、calico、weave,这里我们使用flannel。

#下载此文件
wget https://raw.githubusercontent.com/coreos/flannel/v0.9.1/Documentation/kube-flannel.yml

或直接使用离线包里面的
若要修改网段,需要kubeadm –pod-network-cidr=和这里同步,修改network项。

vim kube-flannel.yml
net-conf.json: |
 65       "Network": "10.244.0.0/16",
 66       "Backend": {
 67         "Type": "vxlan"
 69     }

执行

kubectl create  -f kube-flannel.yml

查看所pod状态,已经都running

[root@master k8s_images]# kubectl get pod --all-namespaces
NAMESPACE     NAME                                           READY     STATUS    RESTARTS   AGE
kube-system   etcd-huaicong-1.novalocal                      1/1       Running   0          2h
kube-system   kube-apiserver-huaicong-1.novalocal            1/1       Running   0          2h
kube-system   kube-controller-manager-huaicong-1.novalocal   1/1       Running   0          2h
kube-system   kube-dns-6f4fd4bdf-j9gd4                       3/3       Running   0          2h
kube-system   kube-flannel-ds-jb66l                          1/1       Running   0          25s
kube-system   kube-proxy-clhpp                               1/1       Running   0          2h
kube-system   kube-scheduler-huaicong-1.novalocal            1/1       Running   0          2h

部署kubernetes-dashboard

kubernetes-dashboard是可选组件,因为,实在不好用,功能太弱了。
建议在部署master时一起把kubernetes-dashboard一起部署了,不然在node节点加入集群后,kubernetes-dashboard会被kube-scheduler调度node节点上,这样根kube-apiserver通信需要额外配置。
下载kubernetes-dashboard的配置文件或直接使用离线包里面的kubernetes-dashboard.yaml

[root@master k8s_images]# kubectl create -f kubernetes-dashboard.yaml 
[root@master k8s_images]# kubectl get pod --all-namespaces
NAMESPACE     NAME                                           READY     STATUS    RESTARTS   AGE
kube-system   etcd-huaicong-1.novalocal                      1/1       Running   0          2h
kube-system   kube-apiserver-huaicong-1.novalocal            1/1       Running   0          2h
kube-system   kube-controller-manager-huaicong-1.novalocal   1/1       Running   0          2h
kube-system   kube-dns-6f4fd4bdf-j9gd4                       3/3       Running   0          2h
kube-system   kube-flannel-ds-jb66l                          1/1       Running   0          25m
kube-system   kube-proxy-clhpp                               1/1       Running   0          2h
kube-system   kube-scheduler-huaicong-1.novalocal            1/1       Running   0          2h
kube-system   kubernetes-dashboard-58f5cb49c-m4f5z           1/1       Running   0          27s
[root@master k8s_images]# kubectl proxy --address=masterip --accept-hosts='^*$'

访问 http: / /masterip:8001/api /v1/namespaces /kube-system/services /https:kubernetes-dashboard:/proxy

node节点操作

修改kubelet配置文件cgroup的driver由systemd改为cgroupfs

vim /etc/systemd/system/kubelet.service.d/10-kubeadm.conf


Environment=”KUBELET_CGROUP_ARGS=–cgroup-driver=cgroupfs”
systemctl daemon-reload
systemctl enable kubelet&&systemctl restart kubelet

使用刚刚执行kubeadm后的kubeadm join –xxx

kubeadm join --token 6c5a50.4fc04fd2f05054ed 192.168.111.123:6443 --discovery-token-ca-cert-hash sha256:fb12670b0c600f310f6d18dae6b19ce7145069afd613dea46bf15be6611306e4

在master节点上检查一下

[root@master




    
 ~]# kubectl get nodes
NAME        STATUS        ROLES     AGE       VERSION
master        Ready     master        14h       v1.9.0
slave1        Ready     <none>        25s       v1.9.0
slave2        Ready     <none>        25s       v1.9.0

测试集群

在master节点上发起个创建应用请求
这里我们创建个名为httpd-app的应用,镜像为httpd,有两个副本pod

kubectl run httpd-app --image=httpd --replicas=2
[root@master ~]# kubectl get deployment
NAME        DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
httpd-app   2         2         2            2           13m
[root@master ~]# kubectl get pods -o wide
NAME                         READY     STATUS    RESTARTS   AGE       IP           NODE
httpd-app-5fbccd7c6c-bbl2c   1/1       Running   0          14m       10.244.1.3   slave1
httpd-app-5fbccd7c6c-ksw9b   1/1       Running   0          14m       10.244.1.4   slave2

因为创建的资源不是service所以不会调用kube-proxy

直接访问测试

[root@master ~]# curl  http://10.244.1.3
<html><body><h1>It works!</h1></body></html>
[root@master ~]# curl  http://10.244.1.4
<html><body><h1>It works!</h1></body></html>
删除应用httpd-app
[root@master ~]# kubectl delete deployment httpd-app
[root@master ~]# kubectl get pods
NAME                         READY     STATUS        RESTARTS   AGE
httpd-app-5fbccd7c6c-bbl2c   0/1       Terminating   0          56m
httpd-app-5fbccd7c6c-ksw9b   0/1       Terminating   0          56m

至此kubernetes基本集群安装完成。

heapster插件部署

下面安装Heapster为集群添加使用统计和监控功能,为Dashboard添加仪表盘。 使用InfluxDB做为Heapster的后端存储,开始部署:

使用到的镜像


mkdir -p ~/k8s/heapster
cd ~/k8s/heapster
wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/grafana.yaml
wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/rbac/heapster-rbac.yaml
wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/heapster.yaml
wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/influxdb.yaml
kubectl create -f ./

最后确认所有的pod都处于running状态,打开Dashboard,集群的使用统计会以仪表盘的形式显示出来

本涉及到安装的镜像

gcr.io/google_containers/kube-proxy-amd64:v1.9.0
gcr.io/google_containers/kube-apiserver-amd64:v1.9.0
gcr.io/google_containers/kube-controller-manager-amd64:v1.9.0
gcr.io/google_containers/kube-scheduler-amd64:v1.9.0
quay.io/coreos/flannel:v0.9.1-amd64
gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.7
gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.7
gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.7
gcr.io/google_containers/etcd-amd64:3.1.10
gcr.io/google_containers/pause-amd64:3.0
gcr.io/google_containers/kubernetes-dashboard-amd64:v1.8.1
gcr.io/google_containers/heapster-influxdb-amd64:v1.3.3
gcr.io/google_containers/heapster-grafana-amd64:v4.4.3
gcr.io/google_containers/heapster-amd64:v1.4.2
一、部署说明1.节点master1:IP:192.168.0.170/24hostname:171master2:IP:192.168.0.171/24hostname:172VIP:192.168.... 来自: ywq935的博客 kubernetes1.11手动搭建本次实验手动搭建一个内部的k8s集群,即不进行认证:1.通过vagrant和virtualbox构建vm.2.设计为一个etcd和一个node,初步,master先... 来自: lemonTree的博客 现象在node节点上日志总是报以下错误[root@node-01ssl]#journalctl-f-ukubelet--Logsbeginat六2018-04-2116:27:19CST.--4月21... 来自: 纵横四海的博客 Kubertenes集群部署Kubertenes集群部署系统环境系统环境初始化安装软件源配置安装docker1.12.6安装kubernetes下载相关镜像初始化kubernetes集群初始化成功输出... 来自: Andriy_dangli kubeadminit命令初始化集群,可以指定KubernetesmasterIP:--apiserver-advertise-address=&amp;lt;ip-address&amp;gt;,如... 来自: qa1986nibuhao的博客 环境说明:192.168.33.15 master-1  master192.168.33.16 node-1  slave192.168.33.17 node-2  slaveecho'192.16... 来自: dest_dest的专栏 This often takes around a minute; or longer if the control plane images have to be pulled. 05-23 有解决方法的欢迎评论或加群:498974515Thisoftentakesaroundaminute;orlongerifthecontrolplaneimageshavetobepulled.roo... 来自: flyer.liu 的博客 环境下载kubernetes和安装1方案1使用阿里云yum镜像2使用国外服务器下载安装包下载kubernetes镜像配置kubelet启动相关组件创建集群配置kubectl的kubeconfig安装f... 来自: zhuchuangang的专栏 2.1kubernetes安装与配置2.1.1安装kubernetesCPU和内存:Master至少1core和2G内存Node至少1core和2G内存Linix操作系统:基于X86_64架构的各种L... 来自: 花名:白起 简介环境信息(采用一个master节点+两个node节点)master192.168.2.110node-1192.168.2.112node-2192.168.2.113操作系统版本:centos7... 来自: liu9718214的专栏 1.脚本auto_deploy_k8s.shimages=(gcr.io/google_containers/kube-proxy-amd64:v1.6.1gcr.io/google_containe... 来自: yjk13703623757的博客 系统信息[root@master~]#cat/etc/redhat-releaseCentOSLinuxrelease7.4.1708(Core)集群环境10.10.9.11master10.10.9... 来自: zuopiezia的博客 系统信息root@ubuntu:~#cat/etc/*releaseDISTRIB_ID=UbuntuDISTRIB_RELEASE=16.04DISTRIB_CODENAME=xenialDISTR... 来自: 迷失的专栏 1.Kubeadm介绍kubeadm是官方提供的工具,用于快速安装一个最小运行的Cluster,因此安装过程中不会安装相关的addons,同时也不会安装相关的网络组件,主要我们自己调用 kubectl... 来自: mark's technic world 1.环境说明[root@k8s-master~]#uname-aLinuxslave14.11.0-22.el7a.aarch64#1SMPSunSep313:39:10CDT2017aarch64a... 来自: smart9527_zc的博客 声明:本文参照官网进行安装,具体请前往官网查看1.环境准备iphostname192.168.1.108master192.168.1.107slave192.168.1.109slave1配置hos... 来自: 纵横四海的博客 1、hostname“master”couldnotbereached在host中没有加解析2、curl-sSLhttp://localhost:10248/healthzcurl:(7)Failed... 来自: kismile 博客园 首页 新随笔 联系 管理 订阅随笔-34 文章-1 评论-2  ETCD搭建 systemd启动etcd服务的时候出现错误:FailedatstepCHDIRspawning/usr/bin/... 来自: 大JAVA解决方案 系统环境[root@kubeadm~]#cat/etc/redhat-releaseCentOSLinuxrelease7.5.1804(Core)关闭selinux[root@kubeadm~]#c... 来自: 纵横四海的博客 安装环境如下:cenos7系统kubeadm安装方法版本是:kubernetes1.10K8s安装完成后,发现所有的pod都起了,除了kube-dns,显示的状态一直是Pending.如下所示:[ro... 来自: 谦190的博客 直接进入主题,先上手,再说别的,也是初次使用,问题一步一步解决。第一步,安装docker,直接安装docker.io就行,我这里的版本是18.06apt-getupdateapt-getinstall... 来自: 有道无德的博客 更多kubernetes文章:k8s专栏目录安装过程见 离线安装k8s1.9.0安装资料参考见 k8s安装1.9版本 官方文档 安装实践离线安装包 视频 课程k8s1.5 与 k8s1.9的差别参照以... 来自: zhd930818的博客 初始化kubeletes集群失败,报错如下:[root@etcd-host1~]#[root@etcd-host1~]#kubeadminit--kubernetes-version=v1.9.0--... 来自: maintain 的博客 在master节点通过kubectl建立calicopolicycontrollercalico-controller.ymlapiVersion:rbac.authorization.k8s.io/... 来自: 陈海峰的博客 要求:1.已存在的k8s集群版本大于v1.1,想要使用NetworkPolicy,需要大于v1.3.02.可以被所有节点访问的etcd集群(可以和k8s共享etcd集群,但是最好建立一个独立的集群)c... 来自: yevvzi的博客 这是kubernetes集群部署的第二部分,在上篇中我们部署了一个的kubernetes集群(4个node节点),接下来我们将部署一些很实用的kubernetes扩展插件,包括集群网络,可视化,服务发... 来自: 紫川秀的博客 简介MultusCNI作为K8S的CNI插件,支持同时添加多个网络接口到K8S环境中的POD。这样的部署方式有利用用户把管理网络和业务网络相互隔离,有效控制容器集群网络架构下图是MultusCNI配置... 来自: 迷失的专栏 任务场景:参考Kubernetes官网知道进行安装。错误场景:root@ubuntu:~#apt-getinstall-ykubeletkubeadmkubectlkubernetes-cniRead... 来自: 日进一步 最近一周在使用colab 挂载Googledrive运行 机器学习代码时突然出现了下面的问题,进入colab环境按照免费使用谷歌的深度学习云服务教程输入下面的配置认证指令:!apt-getinstal... 来自: Lee的博客 使用secureCRT开启SSH2服务连接远程服务器,提示:Theremotesystemrefusedtheconnection.显然被拒绝啦。原因呐?能够想到至少两点:防火墙;远程主机的shhse... 来自: @角色扮演# 基础环境关闭防火墙selinux   1 2   $systemctlstopfirewalld&amp;amp;&amp;amp;systemctldisablefi... 来自: ccy19910925的博客 系统环境系统[root@kubernetes-master-1~]#cat/etc/redhat-releaseCentOSLinuxrelease7.4.1708(Core)hosts[root@k... 来自: 纵横四海的博客 kubernetes集成calico测试环境在物理服务器使用KVM构建了三台虚拟机(4core8G),服务器上的网卡是万兆,虚拟机与虚拟机之间使用KVM的NAT网络模式。三个节点充当kubernete... 来自: wenwenxiong的专栏 使用 kubeadm 安装 kubernetes 1.10.1【centos7.3 离线 安装docker, kubeadm ,kubectl,kubelet,dashboard】 kubernetes v1.10.1 06-25 环境:3台centos7.3虚拟机10.10.31.202k8s-master10.10.31.203k8s-node110.10.31.204k8s-node2环境设置:1.系统升级(所有节点)[r... 来自: 随笔记录-分享&记忆 一、环境准备首先环境还是三台虚拟机,虚拟机地址如下IP地址节点192.168.1.167master192.168.1.189node1192.168.1.176node2然后每台机器安装好docke... 来自: moonpure的专栏 此前,根据在CentOS7.2上部署Kubernetes集群已部署一个可用Kubernetes集群,在这篇文章中将介绍如何为该集群搭建可视化界面。部署KubernetesDashboard根据kube... 来自: Jackson_csdn的博客 集群环境主机名称 IP 备注 操作系统 master 192.168.0.8 docker、kubectl、kubelet、kubeadm、flannel centos7.3... 来自: 菲宇运维 kubernetes(k8s)DNS服务反复重启解决:k8s.io/dns/pkg/dns/dns.go:150:Failedtolist*v1.Service:Gethttps://10.96.0.... 来自: shida's blog kubeadm简介环境准备安装kubeadm简介kubeadm是一个工具包,可帮助您以简单,合理安全和可扩展的方式安装Kubernetes群集。它还支持管理BootstrapTokens和升降级群集版... 来自: ACxlm的博客 为了让产品在迎来业务量爆发式增长前完成应对措施,在浏览无数的资料后,决定将服务逐渐进行容器化,最终能达到容器集群的效果。而容器集群的解决方案中,kubernetes(简称k8s)看起来是个可行的方案。... 来自: Coder编程的博客 本文参考kubernetes官网文章InstallingKubernetesonLinuxwithkubeadm在CentOS7.2使用Kubeadm部署Kuebernetes集群,解决了一些在按照该... 来自: Jackson_csdn的博客 **声明:此文为笔者个人经验,仅供参考**。本文省略的docker的安装,kubernetes的master和work节点都需要安装docker,最好使用指定版本的docker,例如比这安装的是k8s... 来自: russle的专栏 一环境准备1. 修改所有机器hosts文件Master和Node节点修改/etc/hosts文件,加入主机地址192.168.182.128  Master192.168.182.129  Node1... 来自: u013289746的博客 一、概述下面介绍的内容会展示如何在Ubuntu16.04、CentOS7和HypriotOSv1.0.1+操作系统上部署一套安全的Kubernetes集群。下面介绍的安装方式是通过kubeadmin工... 来自: 容器技术爱好者 kubeadm是1.4添加的新功能,使用kubeadm可以轻松的安装集群。1.安装kubelet和kubeadmcat/etc/yum.repos.d/k8s.repo[kubelet]name=ku... 来自: yevvzi的博客 kubectltaintnodes--allnode-role.kubernetes.io/master-         //设置master也可以被调度kubectlexec-itname-xxx... 来自: xcagy-国际性的文档记录中心 1. 关于NodeTaint#kubectltaintnodes`hostname`node-role.kubernetes.io/master:NoSchedule-#kubectltaintnod... 来自: shida's blog 1.kubelet简介在kubernetes集群中,每个Node节点都会启动kubelet进程,用来处理Master节点下发到本节点的任务,管理Pod和其中的容器。kubelet会在APIServer... 来自: 胡伟煌的博客 圣诞献礼!          2012年-2013年,Sunny在CSDN技术博客中陆续发表了100多篇与设计模式相关的文章,涵盖了七个面向对象设计原则和24个设计模式(23个GoF设计模式 +  简... 来自: 刘伟技术博客 打开某个应用程序的配置文件Web.config后,我们会发现以下这段: < sessionState mode="InProc" stateConnectionString="tcpip=1... 来自: yszwn的专栏 0.绪论这篇文章主要为了研究双目立体视觉的最终目标——三维重建,系统的介绍了三维重建的整体步骤。双目立体视觉的整体流程包括:图像获取,摄像机标定,特征提取(稠密匹配中这一步可以省略),立体匹配,三维重... 来自: shiter编写程序的艺术 在虚拟机里安装hadoop,关闭防火墙、配置ip 我的系统环境为:win8系统、vmware11、centos81、设置虚拟机网络通信模式为host only模式 在虚拟机目录... 来自: 梦想的翅膀 卷积神经网络是深度学习的基础,但是学习CNN却不是那么简单,虽然网络上关于CNN的相关代码很多,比较经典的是tiny_cnn(C++)、DeepLearnToolbox(Matlab)等等,但通过C语... 来自: tostq的专栏 单机最大的TCP连接数及其修改 一个误解: 单个服务器程序可承受最大连接数“理论”上是“65535” .    65535这个数字的由来,很多人想当然地将它与port最大值联系起来。的确,TCP的... 来自: 田发江的专栏 最近公司安排了个任务:要求交付一个DLL,实现【PDF转换成图片】,最好的效果是能够掌握所有源码,实在不行才交付第三方DLL。研究了6个工作日+1双休+每晚9点下班,逛遍了国内外各种论坛,还是没能成功... 来自: 劼哥舍 众所周知,Activex组件没有进行有效的签名,在IE上无法安装的,除非你让用户手工开启“接收任何未签名的ActiveX”,这个很明显不现实。而组件签名需要证书,证书从哪里来,你可以选择付1000到3... 来自: jiangtongcn的专栏 上一篇博客介绍了如何解决Fragment重叠的问题,有需要的同学可以看一下,底部有demo下载。 直通车:完美解决Fragment重叠本篇博客我们来说一下怎么让fragment重新加载布局资源文件。... 来自: 喻志强的博客 我们可能经常会用到这一功能,比如有时,我们不希望用户没有进行登录访问后台的操作页面,而且这样的非法访问会让系统极为的不安全,所以我们常常需要进行登录才授权访问其它页面,否则只会出现登录页面,当然我的思... 来自: 沉默的鲨鱼的专栏 我在VC中用ADO调用Sybase ataptive anywhere中的一个专用于用户注册的存储过程时,ADO调用参考了MSDN和一些从网上收集到的样例,但总在执行if(!pRecSet->Ge... 来自: snowglede的专栏 自微软从2013版本推出新的插件注册器后,随着UI的重大更新后,问题也多了很多,前面已有博客提到注册assembly时看不到注册按钮(http://blog.csdn.net/vic0228/arti... 来自: Vic的博客 springmvc文件上传下载实现起来非常简单,此springmvc上传下载案例适合已经搭建好的ssm框架(spring+springmvc+mybatis)使用,ssm框架项目的搭建我相信你们已经搭... 来自: jronzhang的博客 问题场景描述整个项目通过Maven构建,大致结构如下: 核心Spring框架一个module spring-boot-base service和dao一个module server-core 提供系统... 来自: 开发随笔 工作需求,渐变色的边框和文字,还需要显示drawable。我们知道如果是View的背景色渐变,那么很好办,只需要写一个drawable文件,里面定义shape然后设置为View的background就... 来自: 泥巴城 的博客 iOS安全攻防(二十三):Objective-C代码混淆class-dump可以很方便的导出程序头文件,不仅让攻击者了解了程序结构方便逆向,还让着急赶进度时写出的欠完善的程序给同行留下笑柄。所以,我们... 来自: 念茜的博客 测试环境莫名其妙有几条重要数据被删除了,由于在binlog里面只看到是公用账号删除的,无法查询是那个谁在那个时间段登录的,就考虑怎么记录每一个MYSQL账号的登录信息,在MYSQL中,每个连接都会先执... 来自: 路在脚下 以前在博客:基于PYQT编写一个人脸识别软件 中给出了我自己用PYQT编写的一个小软件。鉴于使用的是开源库——face_recogniton,尽管使用很简单,但是还有些问题,比如:识别黄种人时... 来自: hongbin_xu的博客 最近在做一个Mac下的ssh调试工具,但是出现了一点问题。后来发现居然Mac下有串口调试工具可以用,所以果断换串口了,是普通PL2303芯片的usb转串口线。 接下来说下简单的安装步骤吧。我是勤劳的... 来自: Horizen