kubeadm部署k8s
2024-06-18 03:38:47
环境：
| hostname | ip | os |
|---|---|---|
| master | 192.168.86.132 | centos7 |
| node1 | 192.168.86.133 | centos7 |
| node2 | 192.168.86.134 | centos7 |
根据自己需求配置主机名和hosts文件
3台主机
[root@localhost ~]# hostnamectl set-hostname master
[root@localhost ~]# hostnamectl set-hostname node1
[root@localhost ~]# hostnamectl set-hostname node2
断开重连,3台主机配置hosts文件，最终如下
[root@master ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.86.132 master
192.168.86.133 node1
192.168.86.134 node2
配置docker&&kubernetes yum仓库
配置mater节点：docker-ce仓库[root@master ~]# wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repokubernetes仓库[root@master ~]# cat /etc/yum.repos.d/kubernetes.repo [kubernetes]name=kubernetes Repobaseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/gpgcheck=1gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg,https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpgenabled=1验证仓库[root@master ~]# yum repolistLoaded plugins: fastestmirrorLoading mirror speeds from cached hostfile* base: mirrors.tuna.tsinghua.edu.cn* extras: mirrors.tuna.tsinghua.edu.cn* updates: mirror.jdcloud.comrepo id repo name statusbase/7/x86_64 CentOS-7 - Base 10,097docker-ce-stable/x86_64 Docker CE Stable - x86_64 61extras/7/x86_64 CentOS-7 - Extras 305kubernetes kubernetes Repo 430updates/7/x86_64 CentOS-7 - Updates 73配置node1节点：[root@master ~]# scp /etc/yum.repos.d/{docker-ce.repo,kubernetes.repo} root@node1:/etc/yum.repos.d/The authenticity of host 'node1 (192.168.86.133)' can't be established.ECDSA key fingerprint is cd:6d:8f:fe:37:b0:9b:fe:6e:05:21:3e:5a:1d:81:43.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added 'node1' (ECDSA) to the list of known hosts.root@node1's password: docker-ce.repo 100% 2640 2.6KB/s 00:00 kubernetes.repo 100% 199 0.2KB/s 00:00配置node2节点：[root@master ~]# scp /etc/yum.repos.d/{docker-ce.repo,kubernetes.repo} root@node2:/etc/yum.repos.d/The authenticity of host 'node1 (192.168.86.133)' can't be established.ECDSA key fingerprint is cd:6d:8f:fe:37:b0:9b:fe:6e:05:21:3e:5a:1d:81:43.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added 'node1' (ECDSA) to the list of known hosts.root@node1's password: docker-ce.repo 100% 2640 2.6KB/s 00:00 kubernetes.repo 100% 199 0.2KB/s 00:00
安装docker && kubernetes组件
[root@master ~]# yum install docker-ce-18.06.0.ce kubelet-1.11.1 kubeadm-1.11.1 kubectl-1.11.1 -y
若是安装报如下错误
Error: Package: kubelet-1.11.1-0.x86_64 (kubernetes)Requires: kubernetes-cni = 0.6.0Available: kubernetes-cni-0.3.0.1-0.07a8a2.x86_64 (kubernetes)kubernetes-cni = 0.3.0.1-0.07a8a2Available: kubernetes-cni-0.5.1-0.x86_64 (kubernetes)kubernetes-cni = 0.5.1-0Available: kubernetes-cni-0.5.1-1.x86_64 (kubernetes)kubernetes-cni = 0.5.1-1Available: kubernetes-cni-0.6.0-0.x86_64 (kubernetes)kubernetes-cni = 0.6.0-0Installing: kubernetes-cni-0.7.5-0.x86_64 (kubernetes)kubernetes-cni = 0.7.5-0You could try using --skip-broken to work around the problemYou could try running: rpm -Va --nofiles --nodigest
先执行
[root@node1 ~]# yum install kubelet-1.11.1
启动docker服务
启动docker
[root@master ~]# systemctl start docker
[root@master ~]# docker infoContainers: 0Running: 0Paused: 0Stopped: 0Images: 0Server Version: 18.06.0-ceStorage Driver: devicemapperPool Name: docker-253:0-269681803-poolPool Blocksize: 65.54kBBase Device Size: 10.74GBBacking Filesystem: xfsUdev Sync Supported: trueData file: /dev/loop0Metadata file: /dev/loop1Data loop file: /var/lib/docker/devicemapper/devicemapper/dataMetadata loop file: /var/lib/docker/devicemapper/devicemapper/metadataData Space Used: 11.8MBData Space Total: 107.4GBData Space Available: 103GBMetadata Space Used: 581.6kBMetadata Space Total: 2.147GBMetadata Space Available: 2.147GBThin Pool Minimum Free Space: 10.74GBDeferred Removal Enabled: trueDeferred Deletion Enabled: trueDeferred Deleted Device Count: 0Library Version: 1.02.107-RHEL7 (2015-10-14)Logging Driver: json-fileCgroup Driver: cgroupfsPlugins:Volume: localNetwork: bridge host macvlan null overlayLog: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslogSwarm: inactiveRuntimes: runcDefault Runtime: runcInit Binary: docker-initcontainerd version: d64c661f1d51c48782c9cec8fda7604785f93587runc version: 69663f0bd4b60df09991c08812a60108003fa340init version: fec3683Security Options:seccompProfile: defaultKernel Version: 3.10.0-327.el7.x86_64Operating System: CentOS Linux 7 (Core)OSType: linuxArchitecture: x86_64CPUs: 4Total Memory: 1.782GiBName: masterID: NHJ4:5T7H:MUV7:OXHX:MGD4:FV4H:ZLSP:IQ2F:YHBU:UMQX:LNVA:BSQVDocker Root Dir: /var/lib/dockerDebug Mode (client): falseDebug Mode (server): falseRegistry: https://index.docker.io/v1/Labels:Experimental: falseInsecure Registries:127.0.0.0/8Live Restore Enabled: falseWARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.我们查看以下内容可以发现iptables不对bridge的数据进行处理
[root@master ~]# cat /proc/sys/net/bridge/bridge-nf-call-iptables
0
[root@master ~]# cat /proc/sys/net/bridge/bridge-nf-call-ip6tables
0
这里我们将其打开
[root@master ~]# cat /etc/sysctl.conf
# System default settings live in /usr/lib/sysctl.d/00-system.conf.
# To override those settings, enter new settings here, or in an /etc/sysctl.d/<name>.conf file
#
# For more information, see sysctl.conf(5) and sysctl.d(5).
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1[root@master ~]# sysctl -p
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1[root@master ~]# systemctl restart docker
[root@master ~]# systemctl enable docker.service
Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
设置kubelet自启动,但是不要start kubelet,我们还没有完成初始化。
[root@master ~]# systemctl enable kubelet
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
初始化kubelet。node1,node2，容器会有同样的问题，不再赘述
[root@master ~]# vim /etc/sysconfig/kubelet
KUBELET_EXTRA_ARGS="--fail-swap-on=false"
[root@master ~]# kubeadm init --kubernetes-version=v1.11.1 --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/12 --ignore-preflight-errors=Swap好！！现在问题来了
[init] using Kubernetes version: v1.11.1
[preflight] running pre-flight checks[WARNING Swap]: running with swap on is not supported. Please disable swap
I1115 11:39:45.066608 3008 kernel_validator.go:81] Validating kernel version
I1115 11:39:45.066743 3008 kernel_validator.go:96] Validating kernel config[WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 18.06.0-ce. Max validated version: 17.03
[preflight/images] Pulling images required for setting up a Kubernetes cluster
[preflight/images] This might take a minute or two, depending on the speed of your internet connection
[preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull'
[preflight] Some fatal errors occurred:[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-apiserver-amd64:v1.11.1]: exit status 1[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-controller-manager-amd64:v1.11.1]: exit status 1[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-scheduler-amd64:v1.11.1]: exit status 1[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-proxy-amd64:v1.11.1]: exit status 1[ERROR ImagePull]: failed to pull image [k8s.gcr.io/pause:3.1]: exit status 1[ERROR ImagePull]: failed to pull image [k8s.gcr.io/etcd-amd64:3.2.18]: exit status 1[ERROR ImagePull]: failed to pull image [k8s.gcr.io/coredns:1.1.3]: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...简单来说由于某种原因镜像pull不下来
所以请完成下列操作：
去dockerhub搜索mirrorgooglecontainers或直接复制下方链接
https://hub.docker.com/search?q=mirrorgooglecontainers&type=image找到与我们需求对应的镜像版本下载下来，然后修改tag
这里整理了一份我这个版本的image文件。
[root@master ~]# cat docker.txt
mirrorgooglecontainers/kube-apiserver:v1.11.1
mirrorgooglecontainers/kube-controller-manager:v1.11.1
mirrorgooglecontainers/kube-scheduler:v1.11.1
mirrorgooglecontainers/kube-proxy:v1.11.1
mirrorgooglecontainers/pause:3.1
mirrorgooglecontainers/etcd:3.2.18
coredns/coredns:1.1.3
[root@master ~]# for i in `cat docker.txt`;do docker pull $i;done
[root@master ~]# docker images
mirrorgooglecontainers/kube-proxy v1.11.1 d5c25579d0ff 16 months ago 97.8MB
mirrorgooglecontainers/kube-apiserver v1.11.1 816332bd9d11 16 months ago 187MB
mirrorgooglecontainers/kube-controller-manager v1.11.1 52096ee87d0e 16 months ago 155MB
mirrorgooglecontainers/kube-scheduler v1.11.1 272b3a60cd68 16 months ago 56.8MB
mirrorgooglecontainers/etcd 3.2.18 b8df3b177be2 19 months ago 219MB
mirrorgooglecontainers/pause 3.1 da86e6ba6ca1 23 months ago 742kB
coredns/coredns 1.1.3 b3b94275d97c 18 months ago 45.6MB然后再通过docker tag打上我们所需求的标签
例如
[root@master ~]# docker tag mirrorgooglecontainers/etcd:3.2.18 k8s.gcr.io/etcd-amd64:3.2.18
都替换完成，再次执行
[root@master ~]# kubeadm init --kubernetes-version=v1.11.1 --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/12 --ignore-preflight-errors=Swap
最后可以看到如下信息
......
Your Kubernetes master has initialized successfully!To start using your cluster, you need to run the following as a regular user:mkdir -p $HOME/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/configYou 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 192.168.86.132:6443 --token i6q6rl.vwnm24msoi3wn2bu --discovery-token-ca-cert-hash sha256:a8a4b905bd2273bd41eada0a200cbe8d08da16b5ff8e3cce15577a7ca91b58e0
我们可以通过
kubeadm join 192.168.86.132:6443 --token i6q6rl.vwnm24msoi3wn2bu --discovery-token-ca-cert-hash sha256:a8a4b905bd2273bd41eada0a200cbe8d08da16b5ff8e3cce15577a7ca91b58e0
命令将其它node加入集群，此信息最好保存下来。
查看启动端口
[root@master ~]# ss -tnl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 127.0.0.1:10248 *:*
LISTEN 0 128 127.0.0.1:10249 *:*
LISTEN 0 128 127.0.0.1:10251 *:*
LISTEN 0 128 127.0.0.1:2379 *:*
LISTEN 0 128 127.0.0.1:10252 *:*
LISTEN 0 128 127.0.0.1:2380 *:*
LISTEN 0 128 127.0.0.1:53620 *:*
LISTEN 0 128 *:22 *:*
LISTEN 0 100 127.0.0.1:25 *:*
LISTEN 0 128 :::10250 :::*
LISTEN 0 128 :::6443 :::*
LISTEN 0 128 :::10256 :::*
LISTEN 0 128 :::22 :::*
LISTEN 0 100 ::1:25 :::*
查看启动的container
[root@master ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
18be8363820f 272b3a60cd68 "kube-scheduler --ad…" 33 seconds ago Up 25 seconds k8s_kube-scheduler_kube-scheduler-master_kube-system_537879acc30dd5eff5497cb2720a6d64_0
fe11e4df7cb5 52096ee87d0e "kube-controller-man…" 33 seconds ago Up 28 seconds k8s_kube-controller-manager_kube-controller-manager-master_kube-system_4d3dd4aa4977549fcdf9970fd8cc1e2e_0
64f2e26c48fd 816332bd9d11 "kube-apiserver --au…" 34 seconds ago Up 31 seconds k8s_kube-apiserver_kube-apiserver-master_kube-system_ffd3369a9787ba406fc6032257ca8de3_0
c4342dcffb2f b8df3b177be2 "etcd --advertise-cl…" 34 seconds ago Up 32 seconds k8s_etcd_etcd-master_kube-system_d3a295b6d0da8bbfe30c134cab4d030b_0
7aa8bb319858 k8s.gcr.io/pause:3.1 "/pause" 36 seconds ago Up 33 seconds k8s_POD_kube-scheduler-master_kube-system_537879acc30dd5eff5497cb2720a6d64_0
06284b8da33e k8s.gcr.io/pause:3.1 "/pause" 36 seconds ago Up 34 seconds k8s_POD_kube-controller-manager-master_kube-system_4d3dd4aa4977549fcdf9970fd8cc1e2e_0
2d898414f315 k8s.gcr.io/pause:3.1 "/pause" 36 seconds ago Up 34 seconds k8s_POD_kube-apiserver-master_kube-system_ffd3369a9787ba406fc6032257ca8de3_0
5170e84f6bbc k8s.gcr.io/pause:3.1 "/pause" 36 seconds ago Up 35 seconds k8s_POD_etcd-master_kube-system_d3a295b6d0da8bbfe30c134cab4d030b_0[root@master ~]# ls /etc/kubernetes/
admin.conf controller-manager.conf kubelet.conf manifests pki scheduler.conf
配置部署flannel网络 node1,node2不再赘述
[root@master ~]# mkdir -p $HOME/.kube
[root@master ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
获取组件状态信息
[root@master ~]# kubectl get cs
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-0 Healthy {"health": "true"}
获取节点
[root@master ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master NotReady master 50m v1.11.1[root@master ~]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
podsecuritypolicy.policy/psp.flannel.unprivileged created
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.apps/kube-flannel-ds-amd64 created
daemonset.apps/kube-flannel-ds-arm64 created
daemonset.apps/kube-flannel-ds-arm created
daemonset.apps/kube-flannel-ds-ppc64le created
daemonset.apps/kube-flannel-ds-s390x created查看flannel是否成功
[root@master ~]# docker image ls | grep fl
quay.io/coreos/flannel v0.11.0-amd64 ff281650a721 9 months ago 52.5MB查看名称空间
[root@master ~]# kubectl get ns
NAME STATUS AGE
default Active 2h
kube-public Active 2h
kube-system Active 2h查看 kube-system名称空间的pod
[root@master ~]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-78fcdf6894-4j5jb 1/1 Running 0 2h
coredns-78fcdf6894-qghd2 1/1 Running 0 2h
etcd-master 1/1 Running 0 1m
kube-apiserver-master 1/1 Running 0 1m
kube-controller-manager-master 1/1 Running 0 1m
kube-flannel-ds-amd64-bzlmp 1/1 Running 0 3m
kube-proxy-qc82k 1/1 Running 0 2h
kube-scheduler-master 1/1 Running 0 1m
部署node1
[root@node1 ~]# yum install kubelet-1.11.1
[root@node1 ~]# yum install docker-ce-18.06.0.ce kubeadm-1.11.1 kubectl-1.11.1 -y
[root@node1 ~]# cat /etc/sysconfig/kubelet
KUBELET_EXTRA_ARGS="--fail-swap-on=false"
[root@node1 ~]# systemctl start docker
[root@node1 ~]# systemctl enable kubelet docker
[root@node1 ~]# cat /etc/sysctl.conf
# System default settings live in /usr/lib/sysctl.d/00-system.conf.
# To override those settings, enter new settings here, or in an /etc/sysctl.d/<name>.conf file
#
# For more information, see sysctl.conf(5) and sysctl.d(5).
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1[root@node1 ~]# sysctl -p
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1这个kubeadm join为kubeadm init最后生成的信息[root@node1 ~]# kubeadm join 192.168.86.132:6443 --token i6q6rl.vwnm24msoi3wn2bu --discovery-token-ca-cert-hash sha256:a8a4b905bd2273bd41eada0a200cbe8d08da16b5ff8e3cce15577a7ca91b58e0 --ignore-preflight-errors=Swap最后可以看到
....
This node has joined the cluster:
* Certificate signing request was sent to master and a responsewas received.
* The Kubelet was informed of the new secure connection details.Run 'kubectl get nodes' on the master to see this node join the cluster.
....
部署node2
[root@node2 ~]# yum install kubelet-1.11.1
[root@node2 ~]# yum install docker-ce-18.06.0.ce kubeadm-1.11.1 kubectl-1.11.1 -y
[root@node2 ~]# cat /etc/sysconfig/kubelet
KUBELET_EXTRA_ARGS="--fail-swap-on=false"
[root@node2 ~]# systemctl start docker
[root@node2 ~]# systemctl enable kubelet docker[root@node2 ~]# cat /etc/sysctl.conf
# System default settings live in /usr/lib/sysctl.d/00-system.conf.
# To override those settings, enter new settings here, or in an /etc/sysctl.d/<name>.conf file
#
# For more information, see sysctl.conf(5) and sysctl.d(5).
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
[root@node2 ~]# sysctl -p
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1[root@node2 ~]# kubeadm join 192.168.86.132:6443 --token i6q6rl.vwnm24msoi3wn2bu --discovery-token-ca-cert-hash sha256:a8a4b905bd2273bd41eada0a200cbe8d08da16b5ff8e3cce15577a7ca91b58e0 --ignore-preflight-errors=Swap
......
This node has joined the cluster:
* Certificate signing request was sent to master and a responsewas received.
* The Kubelet was informed of the new secure connection details.Run 'kubectl get nodes' on the master to see this node join the cluster.
......
master查看
这里可以看到node已经加了进来，但是node节点还没有启动完成。
[root@master ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master Ready master 3h v1.11.1
node1 NotReady <none> 3m v1.11.1
node2 NotReady <none> 2m v1.11.1可以看到容器正在node节点创建
[root@master ~]# kubectl get pods -n kube-system -o wide
NAME READY STATUS RESTARTS AGE IP NODE
coredns-78fcdf6894-4j5jb 1/1 Running 0 3h 10.244.0.3 master
coredns-78fcdf6894-qghd2 1/1 Running 0 3h 10.244.0.2 master
etcd-master 1/1 Running 0 16m 192.168.86.132 master
kube-apiserver-master 1/1 Running 0 16m 192.168.86.132 master
kube-controller-manager-master 1/1 Running 0 16m 192.168.86.132 master
kube-flannel-ds-amd64-6vlrt 0/1 Init:0/1 0 3m 192.168.86.134 node2
kube-flannel-ds-amd64-bzlmp 1/1 Running 0 18m 192.168.86.132 master
kube-flannel-ds-amd64-jmsl8 0/1 Init:0/1 0 5m 192.168.86.133 node1
kube-proxy-4mldx 0/1 ContainerCreating 0 3m 192.168.86.134 node2
kube-proxy-hlrz9 0/1 ContainerCreating 0 5m 192.168.86.133 node1
kube-proxy-qc82k 1/1 Running 0 3h 192.168.86.132 master
kube-scheduler-master 1/1 Running 0 16m 192.168.86.132 master
kubeadm部署k8s相关推荐
- kubeadm部署K8S集群并使用containerd做容器运行时
kubeadm部署K8S集群并使用containerd做容器运行时(内容全部实战验证有任何问题欢迎留言咨询讨论) 前言 去年12月份,当Kubernetes社区宣布1.20版本之后会逐步弃用docke ...
- 生产环境kubeadm部署k8s（1.23）高可用集群
kubeadm部署k8s高可用集群 1.设备清单 2.各节点下载docker源 3.各节点安装docker服务并加入开机启动 4.各节点配置docker加速器并修改成k8s驱动 5.各节点重启dock ...
- 《云原生之K8s实战》基于kubeadm部署K8S集群
目录 基于kubeadm部署K8S集群 一.环境准备 1.1.主机初始化配置 1.2.部署docker环境
- kubeadm部署K8S并使用containerd做运行时
kubeadm部署K8S并使用containerd做运行时 前言 去年12月份,当Kubernetes社区宣布1.20版本之后会逐步弃用dockershim,当时也有很多自媒体在宣传Kubernete ...
- 【Kubernetes】如何使用Kubeadm部署K8S集群
一 . 准备机器 本次环境采用华为云ECS弹性云服务器部署(也可以使用VMware) vm01(2V4G): Ubuntu_18.04作为K8S master节点 vm02(1V1G): Ubuntu ...
- 【02】Kubernets：使用 kubeadm 部署 K8S 集群
写在前面的话 通过上一节,知道了 K8S 有 Master / Node 组成,但是具体怎么个组成法,就是这一节具体谈的内容.概念性的东西我们会尽量以实验的形式将其复现. 部署 K8S 集群 互联网常 ...
- 使用kubeadm部署k8s(2、k8s集群部署)
1.kube-proxy开启ipvs的前置条件 默认情况下,Kube-proxy将在kubeadm部署的集群中以iptables模式运行,需要注意的是,当内核版本大于4.19时,移除了nf_connt ...
- kubeadm部署k8s集群
1.准备环境 虚拟机操作系统: Centos7 角色 IP Master 192.168.150.140 Node1 192.168.150. ...
- kubeadm部署k8s集群最全最详细
一.安装要求 kubeadm安装kubernetes1.15 在开始之前,部署Kubernetes集群机器需要满足以下几个条件: 1.一台或多台机器(≥3奇数个),操作系统 CentOS7.x(最好是 ...
- 使用Kubeadm部署K8S单节点，速度快于二进制部署
使用Kubeadmin部署K8S单节点,速度快于二进制部署 一. 环境准备 二.所有节点安装docker 三.所有节点安装kubeadm,kubelet和kubectl 四.部署K8S集群 五.安装d ...
最新文章
- 使用Storm实现WordSum
- 企业必须由真正在乎它的人掌控
- 机器视觉：makefile编译调用Caffe框架的C++程序
- JQuery判断radio是否选中，获取选中值
- php 获取权限,php 获取权限列表函数_PHP教程
- 小程序支付成功后跳转页面失败
- MATLAB矩阵元素的处理
- 使用Julia进行图像处理--图像表示与匹配算法
- r语言算巢式设计方差分析_R语言进行方差分析
- js读取文件的内置方法之 FileReader
- 动软代码生成器v2.78Mysql备注生成完美修复dll
- PR菜鸟入门 -- PR下载安装
- 2017onsite比赛游记帖
- 论文排版一步搞定之公式——（公式居中，编号居右）
- openstack instance resize
- 微信手气红包算法 php,微信随机生成红包金额算法php版
- Testin发布众测平台 助开发者发现质量缺陷建立质量体系
- 凸轮挺杆仿真（Simulink）
- Inception神经网络
- JS设置select标签选中的值