kubernetes节点减容与扩容

已于 2023-03-11 22:41:30 修改
阅读量1.6k 收藏 6
点赞数
分类专栏： k8s docker 文章标签： kubernetes docker linux
于 2022-11-18 11:13:55 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_67405599/article/details/127917129
版权

文章目录

前言

k8s分二进制安装与kubeadm安装，本次我刚好有两套部署好的环境，就都试一下减容与缩容
二进制

[root@cm1 pv]# kubectl get nodes -o wide
NAME   STATUS   ROLES    AGE     VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION              CONTAINER-RUNTIME
cm1    Ready    <none>   3d20h   v1.25.0   10.10.21.197   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21
cm2    Ready    <none>   3d20h   v1.25.0   10.10.21.198   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21
cm3    Ready    <none>   3d20h   v1.25.0   10.10.21.199   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21
cn1    Ready    <none>   3d20h   v1.25.0   10.10.21.200   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21
cn2    Ready    <none>   3d20h   v1.25.0   10.10.21.201   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21
cn3    Ready    <none>   3d20h   v1.25.0   10.10.21.202   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21
cn4    Ready    <none>   7m      v1.25.0   10.10.21.205   <none>        CentOS Linux 7 (Core)   6.0.8-1.el7.elrepo.x86_64   docker://20.10.21

kubeadm

root@master1:~/rbd_yaml# kubectl get nodes -o wide
NAME             STATUS   ROLES           AGE   VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
master1.hu.org   Ready    control-plane   37d   v1.25.2   10.10.21.170   <none>        Ubuntu 20.04.5 LTS   5.4.0-131-generic   docker://20.10.12
master2.hu.org   Ready    control-plane   36d   v1.25.2   10.10.21.172   <none>        Ubuntu 20.04.5 LTS   5.4.0-90-generic    docker://20.10.12
master3.hu.org   Ready    control-plane   36d   v1.25.2   10.10.21.175   <none>        Ubuntu 20.04.5 LTS   5.4.0-90-generic    docker://20.10.12
node1.hu.org     Ready    <none>          37d   v1.25.2   10.10.21.171   <none>        Ubuntu 20.04.5 LTS   5.4.0-90-generic    docker://20.10.12
node2.hu.org     Ready    <none>          37d   v1.25.2   10.10.21.173   <none>        Ubuntu 20.04.5 LTS   5.4.0-90-generic    docker://20.10.12
node3.hu.org     Ready    <none>          37d   v1.25.2   10.10.21.176   <none>        Ubuntu 20.04.5 LTS   5.4.0-90-generic    docker://20.10.12

缩容

root@master1:~/rbd_yaml# kubectl get node
NAME             STATUS   ROLES           AGE   VERSION
master1.hu.org   Ready    control-plane   37d   v1.25.2
master2.hu.org   Ready    control-plane   36d   v1.25.2
master3.hu.org   Ready    control-plane   36d   v1.25.2
node1.hu.org     Ready    <none>          37d   v1.25.2
node2.hu.org     Ready    <none>          37d   v1.25.2
node3.hu.org     Ready    <none>          37d   v1.25.2
root@master1:~/rbd_yaml# kubectl cordon  node3.hu.org	# 设置节点不可调度
node/node3.hu.org cordoned
root@master1:~/rbd_yaml# kubectl drain node3.hu.org --delete-emptydir-data --ignore-daemonsets
# 驱逐pod 
node/node3.hu.org already cordoned
Warning: ignoring DaemonSet-managed Pods: kube-flannel/kube-flannel-ds-ff5k4, kube-system/kube-proxy-5pnh5, monitor/node-exporter-65pmz
evicting pod monitor/blackbox-exporter-59b7cc76b-br7p9
evicting pod kubegems/kubegems-argo-cd-app-controller-777d8fffb-4l6nr
evicting pod default/nginx-6768c68f7b-dnt7z
evicting pod default/nginx2-b648d744f-kp925
evicting pod kube-system/coredns-c676cc86f-7l2c8
evicting pod kubegems-local/kubegems-local-kubectl-bf9f98658-7t4jv
evicting pod kubegems/kubegems-mysql-0
evicting pod kubegems/kubegems-dashboard-78bd4449c4-ghn2g
evicting pod kubegems/kubegems-gitea-0
evicting pod kubegems/kubegems-redis-master-0
evicting pod kubernetes-dashboard/kubernetes-dashboard-566f484578-gmnnt
pod/kubegems-dashboard-78bd4449c4-ghn2g evicted
pod/kubernetes-dashboard-566f484578-gmnnt evicted
I1118 02:41:07.415515  137843 request.go:682] Waited for 1.088277469s due to client-side throttling, not priority and fairness, request: GET:https://10.10.21.178:6443/api/v1/namespaces/kubegems/pods/kubegems-argo-cd-app-controller-777d8fffb-4l6nr
pod/nginx-6768c68f7b-dnt7z evicted
pod/blackbox-exporter-59b7cc76b-br7p9 evicted
pod/kubegems-local-kubectl-bf9f98658-7t4jv evicted
pod/nginx2-b648d744f-kp925 evicted
pod/kubegems-redis-master-0 evicted
pod/kubegems-argo-cd-app-controller-777d8fffb-4l6nr evicted
pod/kubegems-gitea-0 evicted
pod/kubegems-mysql-0 evicted
pod/coredns-c676cc86f-7l2c8 evicted
node/node3.hu.org drained
root@master1:~/rbd_yaml# kubectl get node
NAME             STATUS                     ROLES           AGE   VERSION
master1.hu.org   Ready                      control-plane   37d   v1.25.2
master2.hu.org   Ready                      control-plane   36d   v1.25.2
master3.hu.org   Ready                      control-plane   36d   v1.25.2
node1.hu.org     Ready                      <none>          37d   v1.25.2
node2.hu.org     Ready                      <none>          37d   v1.25.2
node3.hu.org     Ready,SchedulingDisabled   <none>          37d   v1.25.2
root@master1:~/rbd_yaml# kubectl delete node node3.hu.org 
node "node3.hu.org" deleted
root@master1:~/rbd_yaml# kubectl get node
NAME             STATUS   ROLES           AGE   VERSION
master1.hu.org   Ready    control-plane   37d   v1.25.2
master2.hu.org   Ready    control-plane   36d   v1.25.2
master3.hu.org   Ready    control-plane   36d   v1.25.2
node1.hu.org     Ready    <none>          37d   v1.25.2
node2.hu.org     Ready    <none>          37d   v1.25.2

扩容

以下操作默认已经装好了容器引擎，完成了安装前必要条件

二进制扩容

拷贝证书到新节点上
[root@cn4 kubernetes]# pwd
/etc/kubernetes
[root@cn4 kubernetes]# scp -r  cn3:/etc/kubernetes/* .
root@cn3's password: 
bootstrap-kubelet.kubeconfig                                                                                                                               100% 2232     3.5MB/s   00:00    
kubelet-conf.yml                                                                                                                                           100% 1628     4.9MB/s   00:00    
kubelet.kubeconfig                                                                                                                                         100% 2302     8.4MB/s   00:00    
kube-proxy.kubeconfig                                                                                                                                      100% 6381    18.6MB/s   00:00    
kube-proxy.yaml                                                                                                                                            100%  825     3.6MB/s   00:00    
ca.pem                                                                                                                                                     100% 1363     5.2MB/s   00:00    
ca-key.pem                                                                                                                                                 100% 1675     1.1MB/s   00:00    
front-proxy-ca.pem
启动kubelet和kube-proxy
[root@cn4 kubernetes]# systemctl start kubelet kube-proxy.service 
[root@cn4 kubernetes]# systemctl status kubelet kube-proxy.service 
● kubelet.service - Kubernetes Kubelet
   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2022-11-18 11:03:16 CST; 9s ago
     Docs: https://github.com/kubernetes/kubernetes
 Main PID: 70687 (kubelet)
    Tasks: 14
   Memory: 31.4M
   CGroup: /system.slice/kubelet.service
           └─70687 /usr/local/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig --kubeconfig=/etc/kubernetes/kubelet.kubeconfig --config=/etc/kubernetes/kub...

Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956399   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"host-local-net-dir\" (UniqueNa...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956482   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"kube-api-access-g2glx\" (Uniqu...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956497   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"lib-modules\" (UniqueName: \"k...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956513   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"sys-fs\" (UniqueName: \"kubern...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956552   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"bpffs\" (UniqueName: \"kuberne...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956572   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"cni-bin-dir\" (UniqueName: \"k...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956586   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"cni-net-dir\" (UniqueName: \"k...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956626   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"cni-log-dir\" (UniqueName: \"k...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956642   70687 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"policysync\" (UniqueName: \"ku...
Nov 18 11:03:17 cn4 kubelet[70687]: I1118 11:03:17.956650   70687 reconciler.go:169] "Reconciler: start to sync state"

● kube-proxy.service - Kubernetes Kube Proxy
   Loaded: loaded (/usr/lib/systemd/system/kube-proxy.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2022-11-18 11:03:16 CST; 9s ago
     Docs: https://github.com/kubernetes/kubernetes
 Main PID: 70688 (kube-proxy)
    Tasks: 5
   Memory: 11.1M
   CGroup: /system.slice/kube-proxy.service
           └─70688 /usr/local/bin/kube-proxy --config=/etc/kubernetes/kube-proxy.yaml --v=2

Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884482   70688 service.go:440] "Adding new service port" portName="kube-system/calico-typha:calico-typha" servicePort="1...67:5473/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884491   70688 service.go:440] "Adding new service port" portName="kube-system/kube-dns:dns" servicePort="10.96.0.10:53/UDP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884498   70688 service.go:440] "Adding new service port" portName="kube-system/kube-dns:dns-tcp" servicePort="10.96.0.10:53/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884504   70688 service.go:440] "Adding new service port" portName="kube-system/kube-dns:metrics" servicePort="10.96.0.10:9153/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884568   70688 service.go:440] "Adding new service port" portName="kube-system/metrics-server:https" servicePort="10.97....193:443/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884579   70688 service.go:440] "Adding new service port" portName="ingress-nginx/ingress-nginx-controller:http" serviceP....189:80/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884587   70688 service.go:440] "Adding new service port" portName="ingress-nginx/ingress-nginx-controller:https" service...189:443/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884595   70688 service.go:440] "Adding new service port" portName="kube-system/default-http-backend" servicePort="10.107....129:80/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884605   70688 service.go:440] "Adding new service port" portName="default/kubernetes:https" servicePort="10.96.0.1:443/TCP"
Nov 18 11:03:17 cn4 kube-proxy[70688]: I1118 11:03:17.884855   70688 proxier.go:1030] "Stale service" protocol="udp" servicePortName="kube-system/kube-dns:dns" clusterIP="10.96.0.10"
Hint: Some lines were ellipsized, use -l to show in full.
# 没报错的话大概率成了，我这边因为证书之前有记录过这个节点，开启服务就直接扩进去了
# 如果没有记录的话kubelt会提示node名字找不到，这个时候需要到master节点操作
 kubectl get csr
 kubectl certificate approve csr-vx866  # csr是上面get出来的

扩容完成检查一下

[root@cm1 pv]# kubectl get node,cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME       STATUS   ROLES    AGE     VERSION
node/cm1   Ready    <none>   3d21h   v1.25.0
node/cm2   Ready    <none>   3d21h   v1.25.0
node/cm3   Ready    <none>   3d21h   v1.25.0
node/cn1   Ready    <none>   3d21h   v1.25.0
node/cn2   Ready    <none>   3d21h   v1.25.0
node/cn3   Ready    <none>   3d21h   v1.25.0
node/cn4   Ready    <none>   7m50s   v1.25.0

NAME                                 STATUS    MESSAGE                         ERROR
componentstatus/scheduler            Healthy   ok                              
componentstatus/controller-manager   Healthy   ok                              
componentstatus/etcd-2               Healthy   {"health":"true","reason":""}   
componentstatus/etcd-1               Healthy   {"health":"true","reason":""}   
componentstatus/etcd-0               Healthy   {"health":"true","reason":""}

kubeadm扩容

master节点生成token
root
@master1:~/rbd_yaml#  kubeadm token create --print-join-command 
kubeadm join 10.10.21.178:6443 --token uo89v1.99wf83u43ntilt41 --discovery-token-ca-cert-hash sha256:44aba1ef82b6b34c40fe748a9c2cd321be91aa3c22dd23e706001b65affb9dc9
新节点扩进来

登录到需要扩容的节点上

root@node3:~# kubeadm join 10.10.21.178:6443 --token uo89v1.99wf83u43ntilt41 --discovery-token-ca-cert-hash sha256:44aba1ef82b6b34c40fe748a9c2cd321be91aa3c22dd23e706001b65affb9dc9 
Found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the 'criSocket' field in the kubeadm configuration file: unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock
To see the stack trace of this error execute with --v=5 or higher
#直接执行master上生成的指令报错

这是因为我容器引擎是docker，我们这边的cri接口不上containerd，所以真实命令应该为

root@node3:~# kubeadm join 10.10.21.178:6443 --token uo89v1.99wf83u43ntilt41 --discovery-token-ca-cert-hash sha256:44aba1ef82b6b34c40fe748a9c2cd321be91aa3c22dd23e706001b65affb9dc9  --cri-socket unix:///run/cri-dockerd.sock
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W1118 02:53:23.454899 2669242 cluster.go:94] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta3", Kind:"ClusterConfiguration"}: strict decoding error: unknown field "apiServer.certSANS"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

扩容成功检查一下

root@master1:~/rbd_yaml# kubectl get node,cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                  STATUS   ROLES           AGE   VERSION
node/master1.hu.org   Ready    control-plane   37d   v1.25.2
node/master2.hu.org   Ready    control-plane   36d   v1.25.2
node/master3.hu.org   Ready    control-plane   36d   v1.25.2
node/node1.hu.org     Ready    <none>          37d   v1.25.2
node/node2.hu.org     Ready    <none>          37d   v1.25.2
node/node3.hu.org     Ready    <none>          18m   v1.25.2

NAME                                 STATUS    MESSAGE             ERROR
componentstatus/scheduler            Healthy   ok                  
componentstatus/controller-manager   Healthy   ok                  
componentstatus/etcd-2               Healthy   {"health":"true"}   
componentstatus/etcd-0               Healthy   {"health":"true"}   
componentstatus/etcd-1               Healthy   {"health":"true"}

小提示
如果遇到如以下的报错，多半是node节点之前没有清除好

[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
	[ERROR FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
	[ERROR Port-10250]: Port 10250 is in use
	[ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists

这时候需要将/etc/kubernetes/下清除掉，然后再关闭kubelet再执行扩容命令即可

k8s-节点扩容
anguoan的博客
11-10 623
k8s-节点扩容
Kubernetes 扩容Master节点详细操作指南
TechEnthusiast的博客
11-22 322
Kubernetes作为云原生应用的编排平台,高可用性是其核心目标之一。默认情况下,Kubernetes集群只有一个Master节点,存在单点故障风险。因此,在生产环境中,建议部署多个Master节点以实现高可用。本文将详细介绍如何对现有Kubernetes集群进行Master节点扩容。
K8S 集群节点扩容
weixin_67050107的博客
06-30 1594
k8s 扩容节点
Kubernetes单Master节点平滑扩容为多Master集群实践指南
qq_38743726的博客
03-07 315
==
node节点扩容
weixin_30293079的博客
02-20 350
node节点扩容： 安装docker 部署 kubelet组件 拷贝admin.conf 拷贝bootstrap.conf 安装cni网络插件 拷贝ca.pem 证书，配置kubelet-config.yml文件中参数需要用到 通过csr请求 配置启动kube-proxy 转载于:https://www.cnblogs.co...
使用kubeadm部署k8s集群03-扩容kube-apiserver到3节点
weixin_34329187的博客
01-19 308
使用kubeadm部署k8s集群03-扩容kube-apiserver到3节点 2018/1/3 扩容 kube-apiserver 到 3 节点 配置 kube-apiserver.yaml 分析 kube-apiserver 依赖的证书 为新节点生成专属证书 下发证书到对应的节点 确认每个节点的 apiserver 是否处于 Running 状态 配置 kube-apiserver.yam...
Redis集群节点扩容
ML908的博客
03-23 1183
文章目录案列概述软件包redis节点扩容1、节点基础环境（两台操作一致）2、安装redis（2台同时安装）3、创建集群4、使用redis-cli启动自动迁移5、迁移后检测各个节点槽的均衡性6、为扩容的主节点添加从节点7、平衡各节点槽数量 案列概述 ​ 某电商大型项目，由于业务大规模升级。项目中的前置缓存节点，已经不能满足当前的业务需求，现在对redis集群扩容一套redis主备节点，对于...
Kubernetes节点扩容规模至2500的历程
Docker的专栏
02-19 4330
我们使用Kubernetes做深度学习的研究已经超过两年。尽管我们最大的工作量直接管理裸云VM，但是Kubernetes提供了快速的迭代周期、具有合理的扩展性以及不含样板代码（a lack of boilerplate），所以在Kubernetes上进行的实验大多都达到了我们预期。我们现在运行着几个Kubernetes集群（一些在云上，一些在物理机机上），其中最大的已经超过2500节点。这些集群运
kubeadm rpm包部署的k8s master节点扩容
wenbo885的博客
03-18 653
k8s 扩容master节点
Kubernetes 节点扩容参数详解：那些你必须知道的小细节
最新发布
weixin_42587823的博客
04-10 846
通过这篇文章，我们详细解析了 Kubernetes 集群伸缩时各参数的作用以及在实际使用中的注意事项。无论是--nodes，还是其它参数，每一项都在帮助你实现一个既灵活又稳定的自动扩容机制。希望这篇博客能让你在面对扩容配置时不再手忙脚乱，而是游刃有余地管理集群，确保你的服务既能迎接流量高峰，也能杜绝资源浪费！如果你有更多心得或疑问，欢迎在评论区留言讨论，我们一起让 Kubernetes 变得更简单、更高效！
Kubernetes自动扩缩容：实现高效资源管理
liuxin33445566的博客
08-23 994
Kubernetes的自动扩缩容功能允许用户根据实际需求动态地调整Pod副本的数量，以应对流量的波动。水平Pod自动扩缩容（Horizontal Pod Autoscaler, HPA）：根据CPU利用率或其他选择的度量标准自动调整Pod副本的数量。集群自动扩缩容（Cluster Autoscaler, CA）：根据集群中所有节点的使用情况自动调整节点的数量。
k8s从入门到放弃(2): 缩扩容&更新
weixin_33770878的博客
03-08 1577
前言 自动缩扩容是现代化的容器调度平台带给我们的最激动人心的一项能力。在上规模的业务系统中我们无时无刻不面临着这样的难题：用户的流量往往随着时间波动，甚至偶尔出现不可预测的峰值（毛刺流量），每当流量增加时都需要手工的对应用进行扩容，峰值流量消失后又需要将扩容的机器回收，运维起来费时费力。 幸运的是，k8s这样的容器调度平台正在逐渐帮助我们解决这样的问题，它带来的AutoScaler功能目前已经支持...
iRpc进阶之节点扩容
sinat_28771747的博客
04-11 356
iRpc选举 iRpc项目地址: gitee: https://gitee.com/willbeahero/iRpc github: https://github.com/BrianApple/iRpc iRpc基于raft选举算法实现服务节点自举,由于iRpc需要集群节点扩容,因此没有直接使用dledger项目作为选举实现框架,不过iRpc在实现选举和节点扩容的过程中,复用了dledger项目相关源代码,并按照iRpc所需做出相关调整,在此再次想dledger项目及作者表示感谢,dledger项目
K8s 二进制扩容node节点方案
喀喀喀的博客
06-03 2165
k8s扩容node节点实战
32-k8s项目实战-01-集群节点扩缩容
2302_79199605的博客
02-28 1847
前期，新节点没有证书，借助token联系apiserver加入集群加入后，apiserver为新节点生成证书，用于以后交互使用；第一个项目，就此结束；
Hadoop大数据应用：HDFS 集群节点扩容
cronaldo91的博客
03-14 2115
（11）查看slaves (hadoop节点)SecondaryNameNode （已部署）ResourceManager（已部署）（7）域名主机名(hadoop节点)(10) 清除日志（node04节点）（14）启动服务 （node04节点）(15) 验证 （hadoop节点）000为KB，000000为MB，NodeManager（已部署）NodeManager（已部署）NodeManager（已部署）NameNode （已部署）DataNode（已部署）DataNode（已部署）
Redis Cluster集群架构部署实现及节点的扩容和缩容
m0_62024703的博客
11-30 2703
redis通过主从或者哨兵机制确实解决了单点失败问题，但是写操作都只发生在master节点，而master节点只有一个，写性能没有提升，因此，在大量的高并发场景下主从加上哨兵机制是支撑不了的，所以我们需要redis cluster来解决这个问题， redis cluster是3.0之后推出的一个技术，也就是相对偏后的一个技术，它可以很好的提升redis集群写操作的性能，也能保证服务的高可用，redis cluster的实现方案是基于所谓分布式的集群解决方案，所谓分布式就是数据不是放在单一的一个主机上，而是
k8s-生产实例——保姆级教程-------查看版本以及升级集群。扩容缩容 master 以及node节点
m0_66705547的博客
01-13 972
看版本以及升级集群。扩容缩容 master 以及node节点
Openstack学习总结之十（定制网络、节点扩容）
zhongliwen1981的专栏
04-07 828
前言 这部分我们定制一个“经典网络”，即提供对内和对外的网络模型。对外由provider网络提供，对内由internal网络提供。 一、准备工作 在VMware的control和compute主机上添加仅主机模型的网卡。 添加完成后启动control和compute主机，然后分别在两个主机中配置新网卡eth1。 cd /etc/sysconfig/network-scripts cp ifcfg-eth0 ifcfg-eth1 vim ifcfg-eth1 NAME=eth1 DEVICE=eth1 I
节点扩容
03-08
</think>### 节点扩容的最佳实践与教程 #### 一、节点扩容的核心逻辑 节点扩容分为**垂直扩容**（提升单节点配置）和**水平扩容**（增加节点数量）。水平扩容需重点关注**数据分片均衡性**和**分布式一致性**，避免...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值