Node節點部署
阿新 • • 發佈：2018-12-30
一、部署kubelect
二進位制包準備 將軟體包從linux-node1複製到linux-node2、linux-node3中去
[[email protected] ~]# cd /usr/local/src/kubernetes/server/bin/ [[email protected]-node1 bin]# cp kubelet kube-proxy /opt/kubernetes/bin/ [[email protected]-node1 bin]# scp kubelet kube-proxy 192.168.56.12:/opt/kubernetes/bin/ [[email protected]-node1 bin]# scp kubelet kube-proxy 192.168.56.13:/opt/kubernetes/bin/
建立角色繫結
[[email protected] bin]# kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap clusterrolebinding.rbac.authorization.k8s.io "kubelet-bootstrap" created
建立 kubelet bootstrapping kubeconfig 檔案 設定叢集引數
[[email protected] bin]# cd /usr/local/src/ssl/ [[email protected]-node1 ssl]# pwd /usr/local/src/ssl [[email protected]-node1 ssl]# kubectl config set-cluster kubernetes \ --certificate-authority=/opt/kubernetes/ssl/ca.pem \ --embed-certs=true \ --server=https://192.168.56.11:6443 \--kubeconfig=bootstrap.kubeconfig Cluster "kubernetes" set.
設定客戶端認證引數
[[email protected] ssl]# kubectl config set-credentials kubelet-bootstrap \ --token=ad6d5bb607a186796d8861557df0d17f \ --kubeconfig=bootstrap.kubeconfig User "kubelet-bootstrap" set.
設定上下文引數
[[email protected] ssl]# kubectl config set-context default \ --cluster=kubernetes \ --user=kubelet-bootstrap \ --kubeconfig=bootstrap.kubeconfig Context "default" created.
選擇預設上下文
[[email protected] ssl]# kubectl config use-context default --kubeconfig=bootstrap.kubeconfig Switched to context "default". [[email protected]-node1 ssl]# ll bootstrap.kubeconfig -rw------- 1 root root 2167 May 31 15:14 bootstrap.kubeconfig [[email protected]-node1 ssl]# cp bootstrap.kubeconfig /opt/kubernetes/cfg #後續如果新增節點，需要把此證書拷貝至節點上 [[email protected]-node1 ssl]# scp bootstrap.kubeconfig 192.168.56.12:/opt/kubernetes/cfg [[email protected]-node1 ssl]# scp bootstrap.kubeconfig 192.168.56.13:/opt/kubernetes/cfg
二、部署kubelet 1.設定CNI支援
#提示所有node節點都要執行此操作 ####################linux-node1節點為master節點############################### [[email protected]-node1 ssl]# mkdir -p /etc/cni/net.d [[email protected]-node1 ssl]# vim /etc/cni/net.d/10-default.conf { "name": "flannel", "type": "flannel", "delegate": { "bridge": "docker0", "isDefaultGateway": true, "mtu": 1400 } } ######################linux-node2節點############################# [[email protected]-node2 ~]# mkdir -p /etc/cni/net.d [[email protected]-node2 ~]# vim /etc/cni/net.d/10-default.conf { "name": "flannel", "type": "flannel", "delegate": { "bridge": "docker0", "isDefaultGateway": true, "mtu": 1400 } } ######################linux-node3節點############################# [[email protected]-node3 ~]# mkdir -p /etc/cni/net.d [[email protected]-node3 ~]# vim /etc/cni/net.d/10-default.conf { "name": "flannel", "type": "flannel", "delegate": { "bridge": "docker0", "isDefaultGateway": true, "mtu": 1400 } }
建立kubelet目錄
[[email protected] ssl]# mkdir /var/lib/kubelet [[email protected]-node2 ~]# mkdir /var/lib/kubelet [[email protected]-node3 ~]# mkdir /var/lib/kubelet
建立kubelet服務配置
[[email protected] ssl]# vim /usr/lib/systemd/system/kubelet.service [Unit] Description=Kubernetes Kubelet Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=docker.service Requires=docker.service [Service] WorkingDirectory=/var/lib/kubelet ExecStart=/opt/kubernetes/bin/kubelet \ --address=192.168.56.11 \ --hostname-override=192.168.56.11 \ --pod-infra-container-image=mirrorgooglecontainers/pause-amd64:3.0 \ --experimental-bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \ --kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \ --cert-dir=/opt/kubernetes/ssl \ --network-plugin=cni \ --cni-conf-dir=/etc/cni/net.d \ --cni-bin-dir=/opt/kubernetes/bin/cni \ --cluster-dns=10.1.0.2 \ --cluster-domain=cluster.local. \ --hairpin-mode hairpin-veth \ --allow-privileged=true \ --fail-swap-on=false \ --logtostderr=true \ --v=2 \ --logtostderr=false \ --log-dir=/opt/kubernetes/log Restart=on-failure RestartSec=5
同步配置
[[email protected] ssl]# scp /usr/lib/systemd/system/kubelet.service 192.168.56.12:/usr/lib/systemd/system/kubelet.service kubelet.service [[email protected]-node1 ssl]# scp /usr/lib/systemd/system/kubelet.service 192.168.56.13:/usr/lib/systemd/system/kubelet.service kubelet.service
[[email protected] ~]# vim /usr/lib/systemd/system/kubelet.service [[email protected]-node2 ~]# cat /usr/lib/systemd/system/kubelet.service [Unit] Description=Kubernetes Kubelet Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=docker.service Requires=docker.service [Service] WorkingDirectory=/var/lib/kubelet ExecStart=/opt/kubernetes/bin/kubelet \ --address=192.168.56.12 \ --hostname-override=192.168.56.12 \ --pod-infra-container-image=mirrorgooglecontainers/pause-amd64:3.0 \ --experimental-bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \ --kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \ --cert-dir=/opt/kubernetes/ssl \ --network-plugin=cni \ --cni-conf-dir=/etc/cni/net.d \ --cni-bin-dir=/opt/kubernetes/bin/cni \ --cluster-dns=10.1.0.2 \ --cluster-domain=cluster.local. \ --hairpin-mode hairpin-veth \ --allow-privileged=true \ --fail-swap-on=false \ --logtostderr=true \ --v=2 \ --logtostderr=false \ --log-dir=/opt/kubernetes/log Restart=on-failure RestartSec=5linux-node2修改kublelete配置
[[email protected] ~]# vim /usr/lib/systemd/system/kubelet.service [[email protected]-node3 ~]# cat /usr/lib/systemd/system/kubelet.service [Unit] Description=Kubernetes Kubelet Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=docker.service Requires=docker.service [Service] WorkingDirectory=/var/lib/kubelet ExecStart=/opt/kubernetes/bin/kubelet \ --address=192.168.56.13 \ --hostname-override=192.168.56.13 \ --pod-infra-container-image=mirrorgooglecontainers/pause-amd64:3.0 \ --experimental-bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \ --kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \ --cert-dir=/opt/kubernetes/ssl \ --network-plugin=cni \ --cni-conf-dir=/etc/cni/net.d \ --cni-bin-dir=/opt/kubernetes/bin/cni \ --cluster-dns=10.1.0.2 \ --cluster-domain=cluster.local. \ --hairpin-mode hairpin-veth \ --allow-privileged=true \ --fail-swap-on=false \ --logtostderr=true \ --v=2 \ --logtostderr=false \ --log-dir=/opt/kubernetes/log Restart=on-failure RestartSec=5linux-node3修改kubelet服務配置
啟動服務
#linux-node1節點可以不啟動，此節點為master節點 [[email protected]-node1 ssl]# systemctl daemon-reload #######################linux-node2啟動Kubelet############### [[email protected]-node2 ~]# systemctl daemon-reload [[email protected]-node2 ~]# systemctl enable kubelet [[email protected]-node2 ~]# systemctl start kubelet #######################linux-node3啟動Kubelet############## [[email protected]-node3 ~]# systemctl daemon-reload [[email protected]-node3 ~]# systemctl enable kubelet [[email protected]-node3 ~]# systemctl start kubelet
檢視服務狀態
systemctl status kubelet
檢視csr請求 注意是在linux-node1上執行
[[email protected] ssl]# kubectl get csr NAME AGE REQUESTOR CONDITION node-csr-4WjZeYEZtU9TO8vFm_KncCEetdiZpXpBxfL-wJ9GRyk 21s kubelet-bootstrap Pending node-csr-zxEKag7ig1-X8RBd_wfuLoblPv7WnwLSNTj-ozXvjGI 24s kubelet-bootstrap Pending
[[email protected] ~]# cd /opt/kubernetes/ssl/ [[email protected]-node2 ssl]# ll total 44 -rw-r--r-- 1 root root 290 May 30 21:10 ca-config.json -rw-r--r-- 1 root root 1001 May 30 21:10 ca.csr -rw------- 1 root root 1675 May 30 21:10 ca-key.pem -rw-r--r-- 1 root root 1359 May 30 21:10 ca.pem -rw------- 1 root root 1675 May 30 22:32 etcd-key.pem -rw-r--r-- 1 root root 1436 May 30 22:32 etcd.pem -rw------- 1 root root 227 May 31 15:30 kubelet-client.key -rw-r--r-- 1 root root 2185 May 31 15:30 kubelet.crt -rw------- 1 root root 1679 May 31 15:30 kubelet.key -rw------- 1 root root 1675 May 31 14:34 kubernetes-key.pem -rw-r--r-- 1 root root 1610 May 31 14:34 kubernetes.pem在linux-node2節點上檢視，在服務端未批准前檢視證書
[[email protected] ~]# cd /opt/kubernetes/ssl/ [[email protected]-node3 ssl]# ll total 44 -rw-r--r-- 1 root root 290 May 30 21:11 ca-config.json -rw-r--r-- 1 root root 1001 May 30 21:11 ca.csr -rw------- 1 root root 1675 May 30 21:11 ca-key.pem -rw-r--r-- 1 root root 1359 May 30 21:11 ca.pem -rw------- 1 root root 1675 May 30 22:32 etcd-key.pem -rw-r--r-- 1 root root 1436 May 30 22:32 etcd.pem -rw------- 1 root root 227 May 31 15:30 kubelet-client.key -rw-r--r-- 1 root root 2185 May 31 15:30 kubelet.crt -rw------- 1 root root 1675 May 31 15:30 kubelet.key -rw------- 1 root root 1675 May 31 14:34 kubernetes-key.pem -rw-r--r-- 1 root root 1610 May 31 14:34 kubernetes.pem在linux-node3節點上檢視，在服務端未批准前檢視證書
批准kubelet的TLS證書請求
[[email protected] ssl]# kubectl get csr|grep 'Pending' | awk 'NR>0{print $1}'| xargs kubectl certificate approve certificatesigningrequest.certificates.k8s.io "node-csr-4WjZeYEZtU9TO8vFm_KncCEetdiZpXpBxfL-wJ9GRyk" approved certificatesigningrequest.certificates.k8s.io "node-csr-zxEKag7ig1-X8RBd_wfuLoblPv7WnwLSNTj-ozXvjGI" approved [[email protected]-node1 ssl]# kubectl get csr NAME AGE REQUESTOR CONDITION node-csr-4WjZeYEZtU9TO8vFm_KncCEetdiZpXpBxfL-wJ9GRyk 3m kubelet-bootstrap Approved,Issued node-csr-zxEKag7ig1-X8RBd_wfuLoblPv7WnwLSNTj-ozXvjGI 3m kubelet-bootstrap Approved,Issued
執行完畢後，檢視節點狀態已經是Ready的狀態了
[[email protected] ssl]# kubectl get node NAME STATUS ROLES AGE VERSION 192.168.56.12 Ready <none> 3m v1.10.1 192.168.56.13 Ready <none> 3m v1.10.1
[[email protected] ssl]# ll kubelet* -rw-r--r-- 1 root root 1046 May 31 15:33 kubelet-client.crt -rw------- 1 root root 227 May 31 15:30 kubelet-client.key -rw-r--r-- 1 root root 2185 May 31 15:30 kubelet.crt -rw------- 1 root root 1679 May 31 15:30 kubelet.key在linux-node2上檢視，服務端批准後檢視證書
[[email protected] ssl]# ll kubelet* -rw-r--r-- 1 root root 1046 May 31 15:33 kubelet-client.crt -rw------- 1 root root 227 May 31 15:30 kubelet-client.key -rw-r--r-- 1 root root 2185 May 31 15:30 kubelet.crt -rw------- 1 root root 1675 May 31 15:30 kubelet.key在linux-node3上檢視，服務端批准後檢視證書
三、部署kubernetes Proxy
配置kube-proxy使用LVS
[[email protected] ssl]# yum install -y ipvsadm ipset conntrack [[email protected]-node2 ssl]# yum install -y ipvsadm ipset conntrack [[email protected]-node3 ssl]# yum install -y ipvsadm ipset conntrack
建立kube-proxy證書請求
[[email protected] ssl]# vim kube-proxy-csr.json { "CN": "system:kube-proxy", "hosts": [], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "ST": "BeiJing", "L": "BeiJing", "O": "k8s", "OU": "System" } ] }
生成證書
[[email protected] ssl]# cfssl gencert -ca=/opt/kubernetes/ssl/ca.pem \ -ca-key=/opt/kubernetes/ssl/ca-key.pem \ -config=/opt/kubernetes/ssl/ca-config.json \ -profile=kubernetes kube-proxy-csr.json | cfssljson -bare kube-proxy 2018/05/31 15:47:07 [INFO] generate received request 2018/05/31 15:47:07 [INFO] received CSR 2018/05/31 15:47:07 [INFO] generating key: rsa-2048 2018/05/31 15:47:08 [INFO] encoded CSR 2018/05/31 15:47:08 [INFO] signed certificate with serial number 686335705927831639688007943181627318620328401639 2018/05/31 15:47:08 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for websites. For more information see the Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org); specifically, section 10.2.3 ("Information Requirements").
分發證書至所有Node節點
[[email protected] ssl]# cp kube-proxy*.pem /opt/kubernetes/ssl/ [[email protected]-node1 ssl]# scp kube-proxy*.pem 192.168.56.12:/opt/kubernetes/ssl/ [[email protected]-node1 ssl]# scp kube-proxy*.pem 192.168.56.13:/opt/kubernetes/ssl/
建立kube-proxy配置檔案
[[email protected] ssl]# kubectl config set-cluster kubernetes \ --certificate-authority=/opt/kubernetes/ssl/ca.pem \ --embed-certs=true \ --server=https://192.168.56.11:6443 \ --kubeconfig=kube-proxy.kubeconfig Cluster "kubernetes" set. [[email protected]-node1 ssl]# ll kube-proxy* -rw-r--r-- 1 root root 1009 May 31 15:47 kube-proxy.csr -rw-r--r-- 1 root root 230 May 31 15:46 kube-proxy-csr.json -rw------- 1 root root 1679 May 31 15:47 kube-proxy-key.pem -rw------- 1 root root 2011 May 31 15:48 kube-proxy.kubeconfig -rw-r--r-- 1 root root 1403 May 31 15:47 kube-proxy.pem [[email protected]-node1 ssl]# kubectl config set-credentials kube-proxy \ --client-certificate=/opt/kubernetes/ssl/kube-proxy.pem \ --client-key=/opt/kubernetes/ssl/kube-proxy-key.pem \ --embed-certs=true \ --kubeconfig=kube-proxy.kubeconfig User "kube-proxy" set. [[email protected]-node1 ssl]# kubectl config set-context default \ --cluster=kubernetes \ --user=kube-proxy \ --kubeconfig=kube-proxy.kubeconfig Context "default" created. [[email protected]-node1 ssl]# kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig Switched to context "default".
分發kubeconfig配置檔案
[[email protected] ssl]# cp kube-proxy.kubeconfig /opt/kubernetes/cfg/ [[email protected]-node1 ssl]# scp kube-proxy.kubeconfig 192.168.56.12:/opt/kubernetes/cfg/ [[email protected]-node1 ssl]# scp kube-proxy.kubeconfig 192.168.56.13:/opt/kubernetes/cfg/
建立kube-proxy服務配置
[[email protected] ssl]# mkdir /var/lib/kube-proxy
[[email protected] ssl]# mkdir /var/lib/kube-proxy
[[email protected] ssl]# mkdir /var/lib/kube-proxy
[[email protected]-node1 ssl]# vim /usr/lib/systemd/system/kube-proxy.service [Unit] Description=Kubernetes Kube-Proxy Server Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=network.target [Service] WorkingDirectory=/var/lib/kube-proxy ExecStart=/opt/kubernetes/bin/kube-proxy \ --bind-address=192.168.56.11 \ --hostname-override=192.168.56.11 \ --kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig \ --masquerade-all \ --feature-gates=SupportIPVSProxyMode=true \ --proxy-mode=ipvs \ --ipvs-min-sync-period=5s \ --ipvs-sync-period=5s \ --ipvs-scheduler=rr \ --logtostderr=true \ --v=2 \ --logtostderr=false \ --log-dir=/opt/kubernetes/log Restart=on-failure RestartSec=5 LimitNOFILE=65536 [Install] WantedBy=multi-user.target [[email protected]-node1 ssl]# scp /usr/lib/systemd/system/kube-proxy.service 192.168.56.12:/usr/lib/systemd/system/kube-proxy.service [[email protected]-node1 ssl]# scp /usr/lib/systemd/system/kube-proxy.service 192.168.56.13:/usr/lib/systemd/system/kube-proxy.service
[[email protected] ssl]# vim /usr/lib/systemd/system/kube-proxy.service [[email protected]-node2 ssl]# cat /usr/lib/systemd/system/kube-proxy.service [Unit] Description=Kubernetes Kube-Proxy Server Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=network.target [Service] WorkingDirectory=/var/lib/kube-proxy ExecStart=/opt/kubernetes/bin/kube-proxy \ --bind-address=192.168.56.12 \ --hostname-override=192.168.56.12 \ --kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig \ --masquerade-all \ --feature-gates=SupportIPVSProxyMode=true \ --proxy-mode=ipvs \ --ipvs-min-sync-period=5s \ --ipvs-sync-period=5s \ --ipvs-scheduler=rr \ --logtostderr=true \ --v=2 \ --logtostderr=false \ --log-dir=/opt/kubernetes/log Restart=on-failure RestartSec=5 LimitNOFILE=65536 [Install] WantedBy=multi-user.targetlinux-node2修改kube-proxy服務配置
[[email protected] ssl]# cat /usr/lib/systemd/system/kube-proxy.service [Unit] Description=Kubernetes Kube-Proxy Server Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=network.target [Service] WorkingDirectory=/var/lib/kube-proxy ExecStart=/opt/kubernetes/bin/kube-proxy \ --bind-address=192.168.56.13 \ --hostname-override=192.168.56.13 \ --kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig \ --masquerade-all \ --feature-gates=SupportIPVSProxyMode=true \ --proxy-mode=ipvs \ --ipvs-min-sync-period=5s \ --ipvs-sync-period=5s \ --ipvs-scheduler=rr \ --logtostderr=true \ --v=2 \ --logtostderr=false \ --log-dir=/opt/kubernetes/log Restart=on-相關推薦
Kubernetes（K8s）安裝部署過程（六）--node節點部署
sch wan tool pods systemd tps stat mis type hi，everybody，我回來了，之前安裝到flannel之後，文章一直沒有更新，甚至不少小夥伴都來加qq詢問是否繼續更新了， 這裏說明下原因，我在部署1.91node的時候的確出現
Kubernetes集群部署之五node節點部署
啟動 proxy配置 $1 vsp serve desc reload fig rri 部署kubelet: 1.二進制包準備 將軟件包可執行文件從k8s-master復制到node節點中去。 [root@k8s-master ~]# cd /usr/local/src/
手動安裝K8s第六節：node節點部署-kubelet
docker k8s kubernetes 容器 部署kubelet1、準備二進制包[root@k8smaster ~]# cd /usr/local/src/kubernetes/server/bin/ [root@k8smaster bin]# scp kubelet kube-proxy
手動安裝K8s第七節：node節點部署-kube-proxy
docker k8s kubernetes 容器 部署Kubernetes Proxy vim CentOS-Base.repo [base]name=CentOS-$releasever - Base#mirrorlist=http://mirrorlist.centos.org/?rele
二進制安裝kubernetes v1.11.2 （第十一章 node節點部署）
tab flanneld tar ips html apt www. span 1.2 繼續前一章部署。 十一、node節點部署 kubernetes node 節點運行了如下組件： flannel docker kubelet kube-proxy 11.1 部署fl
Kubernetes部署（七）：Node節點部署
node只需安裝kubelet服務，所有節點都需要安裝kube-proxy 部署kubelet 1.二進位制包準備將軟體包從複製到所有node中去。 [[email protected] ~]# cd /usr/local/src/kubernetes/server/bin/ [[email&
Node節點部署
一、部署kubelect 二進位制包準備 將軟體包從linux-node1複製到linux-node2、linux-node3中去 [[email protected] ~]# cd /usr/local/src/kubernetes/server/bin/ [[email pr
K8S二進制部署node節點
k8s node binary 本文介紹node節點的二進制部署過程。 一、軟件包下載地址Node包：https://dl.k8s.io/v1.9.6/kubernetes-node-linux-amd64.tar.gz # tar -zxvpf kubernetes-node-linux-amd
5.K8S部署-------- 部署Node節點
docker k8s 雲計算 虛擬換 Kubernetes 沒有特別其他說明一切按照文檔執行1.二進制包準備 將軟件包從linux-node1復制到linux-node2 linux-node3中去。[root@linux-node1 ~]# cd /usr/local/src/kuber
Kubernetes(k8s)集群部署（k8s企業級Docker容器集群管理）系列之部署master/node節點組件（四）
clas -- ken let 發現 特殊 ref uber scp 0、前言 整體架構目錄：ASP.NET Core分布式項目實戰-目錄 k8s架構目錄：Kubernetes(k8s)集群部署（k8s企業級Docker容器集群管理）系列目錄 1、部署master組
CentOS7環境部署kubenetes1.12版本五部曲之三：node節點加入
本文是《CentOS7環境部署kubenetes1.12版本五部曲》系列的第三篇，上篇文章建立了kubernetes環境的master節點，本章的目標是在kubernetes環境加入node節點，並在上面部署Pod和Service進行驗證； 準備node節點機器
Kubernetes多master部署（5）---創建Node節點kubeconfig文件
spa boot pro .sh str conf rap embed ont 在Master01上執行kubeconfig.sh腳本 cd /opt/ssl #cat kubeconfig.sh # 創建 TLS Bootstrapping Token
三、安裝並配置Kubernetes Node節點
vim rgs conf clu leg -a 管理系 redhat pri 1. 安裝並配置Kubernetes Node節點 1.1 安裝Kubernetes Node節點所需服務 yum -y install kubernetes ? 通過yum安裝kubernete
第10章 文檔對象模型DOM 10.1 Node節點類型
not 應該 特定 新增 ssi 方式 new ext prot DOM是針對 HTML 和 XML 文檔的一個 API（應用程序編程接口） 。DOM描繪了一個層次化的節點樹，允許開發人員添加、移除和修改頁面的某一部分。DOM 脫胎於Netscape 及微軟公司創始的 DH
Redis單節點部署
keepal sna data 兩種 進程id effect err clust cli 安裝Redis 由於REDIS使用單線程處理請求，CPU的快慢最對REDIS的性能有較大影響，官方建議INTEL的CPU，其效率能比AMD高一倍左右。 下載Redis：wget htt
Node.js部署到服務器之後臺守護進程管理器Forever
系統 pan 方式 ins start 進入 all 命令 rest 我們不可能直接通過node命令來管理遠程站點，這樣無法保證網站的可持續運行。我們用Forever來解決這個問題，它可以將NodeJS應用以後臺守護進程的方式運行，我們還可以將NodeJS應用設成隨系統啟動
關於elasticsearch node 節點不可用的故障分析
內核內核內核內核內核開發那邊在搭建集群的時候，無論如何測試，node 節點就是連不上，始終報錯誤org.elasticsearch.client.transport.NoNodeAvailableException: No node available後開看了下，本地環境，原因是回話時間太多，而他的本地環境並
4.K8S部署-------- Master節點部署
docker k8s 雲計算 虛擬化 Kubernetes 部署Kubernetes API服務部署如果沒有特別指定在那臺服務器執行命令。只需要按照文中的步驟執行即可0.準備軟件包[root@linux-node1 ~]# cd /usr/local/src/kubernetes
一、最新Kafka單節點部署+測試 完整
.sh 完整 config pan 安裝文件 什麽 部署 每次 版本 每次學一個東西從基礎的開始，循序漸進。 不急不躁，路還很長。 所有教程都是學習汪文君大神的kafka教程的。 一、部署 這裏選的kafka版本是 0.10.2.1 下載連接 https://downl
docker-swarm容器固定到node節點啟動
新的 反向代理 java_home const nal tomcat placement compose span Docker-compose的編排首先這裏需要創建一個目錄mkdir /docker-compose然後在裏邊創建一個docke