当前位置:网站首页>Kubernetes binary installation (v1.20.16) (IV) deployment master
Kubernetes binary installation (v1.20.16) (IV) deployment master
2022-06-09 03:39:00 【Look, the future】
List of articles
Since the signing CA certificate
Generate CA Certificate configuration
cd /opt/TLS/k8s/ssl
cat > ca-config.json << EOF { "signing": { "default": { "expiry": "87600h" }, "profiles": { "kubernetes": { "expiry": "87600h", "usages": [ "signing", "key encipherment", "server auth", "client auth" ] } } } } EOF
cat > ca-csr.json << EOF { "CN": "kubernetes", "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "L": "Beijing", "ST": "Beijing", "O": "k8s", "OU": "System" } ] } EOF
Generate CA certificate
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
# View the generated certificate file
[[email protected] ssl]# ll
total 20
-rw-r--r-- 1 root root 294 Apr 3 13:37 ca-config.json
-rw-r--r-- 1 root root 1001 Apr 3 13:38 ca.csr
-rw-r--r-- 1 root root 264 Apr 3 13:37 ca-csr.json
-rw------- 1 root root 1675 Apr 3 13:38 ca-key.pem
-rw-r--r-- 1 root root 1310 Apr 3 13:38 ca.pem
# It's generated here ca.pem and ca-key.pem Two documents
Deploy Apiserver
cat > server-csr.json << EOF { "CN": "kubernetes", "hosts": [ "10.0.0.1", "127.0.0.1", "192.168.190.147", "192.168.190.148", "kubernetes", "kubernetes.default", "kubernetes.default.svc", "kubernetes.default.svc.cluster", "kubernetes.default.svc.cluster.local" ], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "L": "BeiJing", "ST": "BeiJing", "O": "k8s", "OU": "System" } ] } EOF
# The above documents hosts Field IP For all Master IP, Not one less ! In order to facilitate later expansion, you can write more reserved IP
Issue apiserver certificate
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server
[[email protected] ssl]# ll
total 36
-rw-r--r-- 1 root root 294 Apr 3 13:37 ca-config.json
-rw-r--r-- 1 root root 1001 Apr 3 13:38 ca.csr
-rw-r--r-- 1 root root 264 Apr 3 13:37 ca-csr.json
-rw------- 1 root root 1675 Apr 3 13:38 ca-key.pem
-rw-r--r-- 1 root root 1310 Apr 3 13:38 ca.pem
-rw-r--r-- 1 root root 1261 Apr 3 13:55 server.csr
-rw-r--r-- 1 root root 557 Apr 3 13:55 server-csr.json
-rw------- 1 root root 1675 Apr 3 13:55 server-key.pem
-rw-r--r-- 1 root root 1627 Apr 3 13:55 server.pem
# It's generated here server.pem and server-key.pem Two documents
create profile
cat > kube-apiserver.conf << EOF KUBE_APISERVER_OPTS="--logtostderr=false \\ --v=2 \\ --log-dir=/opt/kubernetes/logs \\ --insecure-port=0 \\ --etcd-servers=https://192.168.190.147:2379,https://192.168.190.148:2379 \\ --bind-address=192.168.190.147 \\ --secure-port=6443 \\ --advertise-address=192.168.190.147 \\ --allow-privileged=true \\ --service-cluster-ip-range=10.0.0.0/24 \\ --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \\ --authorization-mode=RBAC,Node \\ --enable-bootstrap-token-auth=true \\ --token-auth-file=/opt/kubernetes/cfg/token.csv \\ --service-node-port-range=30000-32767 \\ --kubelet-client-certificate=/opt/kubernetes/ssl/server.pem \\ --kubelet-client-key=/opt/kubernetes/ssl/server-key.pem \\ --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname,InternalDNS,ExternalDNS \\ --tls-cert-file=/opt/kubernetes/ssl/server.pem \\ --tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \\ --client-ca-file=/opt/kubernetes/ssl/ca.pem \\ --service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \\ --service-account-issuer=api \\ --service-account-signing-key-file=/opt/kubernetes/ssl/server-key.pem \\ --etcd-cafile=/opt/etcd/ssl/ca.pem \\ --etcd-certfile=/opt/etcd/ssl/server.pem \\ --etcd-keyfile=/opt/etcd/ssl/server-key.pem \\ --requestheader-client-ca-file=/opt/kubernetes/ssl/ca.pem \\ --proxy-client-cert-file=/opt/kubernetes/ssl/server.pem \\ --proxy-client-key-file=/opt/kubernetes/ssl/server-key.pem \\ --requestheader-allowed-names=kubernetes \\ --requestheader-extra-headers-prefix=X-Remote-Extra- \\ --requestheader-group-headers=X-Remote-Group \\ --requestheader-username-headers=X-Remote-User \\ --enable-aggregator-routing=true \\ --audit-log-maxage=30 \\ --audit-log-maxbackup=3 \\ --audit-log-maxsize=100 \\ --audit-log-path=/opt/kubernetes/logs/k8s-audit.log" EOF
# The top two \\ The first is the escape character , The second is the line break , The escape character is used to use EOF Keep line breaks .
# • --logtostderr: log enable
# • ---v: The log level
# • --log-dir: Log directory
# • --etcd-servers:etcd The cluster address
# • --bind-address: Monitor address
# • --secure-port:https Secure port
# • --advertise-address: Cluster notification address
# • --allow-privileged: Enable authorization
# • --service-cluster-ip-range:Service fictitious IP Address segment
# • --enable-admission-plugins: Access control module
# • --authorization-mode: Certificate authority , Enable RBAC Authorization and node self management
# • --enable-bootstrap-token-auth: Enable TLS bootstrap Mechanism
# • --token-auth-file:bootstrap token file
# • --service-node-port-range:Service nodeport Type default assignment port range
# • --kubelet-client-xxx:apiserver visit kubelet Client certificate
# • --tls-xxx-file:apiserver https certificate
# • 1.20 The parameters that must be added in the above version :--service-account-issuer,--service-account-signing-key-file
# • --etcd-xxxfile: Connect Etcd Cluster Certificate
# • --audit-log-xxx: The audit log
# • Start the aggregation layer configuration :
# • --requestheader-client-ca-file,--proxy-client-cert-file,--proxy-client-key-file,
# • --requestheader-allowed-names,--requestheader-extra-headers-prefix,
# • --requestheader-group-headers,--requestheader-username-headers,
# • --enable-aggregator-routing
Enable TLS Bootstrapping Mechanism
TLS Bootstraping:Master apiserver Enable TLS After certification ,Node node kubelet and kube-proxy To work with kube-apiserver communicate , You have to use CA Only a valid certificate can be issued , When Node When there are many nodes , This kind of client certificate issuance takes a lot of work , It also increases the complexity of cluster expansion . To simplify the process ,Kubernetes Introduced TLS bootstraping Mechanism to automatically issue client certificates ,kubelet It will automatically send the apiserver Apply for a certificate ,kubelet Certificate of by apiserver Dynamic signing . So it's highly recommended that Node In this way , At present, it is mainly used for kubelet,kube-proxy Or we will issue a certificate .
# establish token file
cat > token.csv << EOF c47ffb939f5ca36231d9e3121a252940,kubelet-bootstrap,10001,"system:node-bootstrapper" EOF
# Format :token, user name ,UID, User group
# token You can also generate your own replacement :
# head -c 16 /dev/urandom | od -An -t x | tr -d ' '
Here is a string of token, Don't hesitate , Write it down .
Create management files
cat > kube-apiserver.service << EOF [Unit] Description=Kubernetes API Server Documentation=https://github.com/kubernetes/kubernetes [Service] EnvironmentFile=/opt/kubernetes/cfg/kube-apiserver.conf ExecStart=/opt/kubernetes/bin/kube-apiserver \$KUBE_APISERVER_OPTS Restart=on-failure [Install] WantedBy=multi-user.target EOF
# View the relevant files generated by the above command
[[email protected] cfg]# ll
total 12
-rw-r--r-- 1 root root 1815 Apr 3 13:57 kube-apiserver.conf
-rw-r--r-- 1 root root 286 Apr 3 14:06 kube-apiserver.service
-rw-r--r-- 1 root root 84 Apr 3 13:57 token.csv
Distribute documents
# establish kubernetes Catalog
mkdir -p /opt/kubernetes/{
bin,cfg,ssl,logs}
# Copy certificate file
scp -r /opt/TLS/k8s/ssl/*pem /opt/kubernetes/ssl/
# Copy configuration file
scp -r /opt/TLS/k8s/cfg/token.csv /opt/kubernetes/cfg/
scp /opt/TLS/k8s/cfg/kube-apiserver.conf /opt/kubernetes/cfg/kube-apiserver.conf
# Copy management files
scp /opt/TLS/k8s/cfg/kube-apiserver.service /usr/lib/systemd/system/kube-apiserver.service
# Copy the executable file
scp /opt/TLS/download/kubernetes/server/bin/{
kube-apiserver,kube-scheduler,kube-controller-manager} /opt/kubernetes/bin
scp /opt/TLS/download/kubernetes/server/bin/kubectl /usr/local/bin/
Check the documents
# Check the certificate file
[[email protected] cfg]# ll /opt/kubernetes/ssl/
total 16
-rw------- 1 root root 1675 Apr 3 14:11 ca-key.pem
-rw-r--r-- 1 root root 1310 Apr 3 14:11 ca.pem
-rw------- 1 root root 1675 Apr 3 14:11 server-key.pem
-rw-r--r-- 1 root root 1627 Apr 3 14:11 server.pem
# Check the configuration file
[[email protected] cfg]# ll /opt/kubernetes/cfg/token.csv
-rw-r--r-- 1 root root 84 Apr 3 14:11 /opt/kubernetes/cfg/token.csv
[[email protected] cfg]# ll /opt/kubernetes/cfg/kube-apiserver.conf
-rw-r--r-- 1 root root 1815 Apr 3 14:12 /opt/kubernetes/cfg/kube-apiserver.conf
# Check the management documents
[[email protected] cfg]# ll /usr/lib/systemd/system/kube-apiserver.service
-rw-r--r-- 1 root root 286 Apr 3 14:11 /usr/lib/systemd/system/kube-apiserver.service
# Check executable documents
[[email protected] cfg]# ll /opt/kubernetes/bin/{kube-apiserver,kube-scheduler,kube-controller-manager}
-rwxr-xr-x 1 root root 131301376 Apr 3 14:12 /opt/kubernetes/bin/kube-apiserver
-rwxr-xr-x 1 root root 121110528 Apr 3 14:12 /opt/kubernetes/bin/kube-controller-manager
-rwxr-xr-x 1 root root 49618944 Apr 3 14:12 /opt/kubernetes/bin/kube-scheduler
[[email protected] cfg]# ll /usr/local/bin/kubectl
-rwxr-xr-x 1 root root 46592000 Apr 3 14:12 /usr/local/bin/kubectl
start-up kube-apiserver
[[email protected] cfg]# systemctl daemon-reload && systemctl start kube-apiserver && systemctl enable kube-apiserver && systemctl status kube-apiserver
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-apiserver.service to /usr/lib/systemd/system/kube-apiserver.service.
● kube-apiserver.service - Kubernetes API Server
Loaded: loaded (/usr/lib/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-04-03 14:14:54 CST; 111ms ago
Docs: https://github.com/kubernetes/kubernetes
Main PID: 11765 (kube-apiserver)
CGroup: /system.slice/kube-apiserver.service
└─11765 /opt/kubernetes/bin/kube-apiserver --logtostderr=false --v=2 --log-dir=/opt/kubernetes/logs --insecure-port=0 --etcd-servers=https://192.168.190.147:2379,https://192.168.190.148:2379
Apr 03 14:14:54 k8s-master systemd[1]: Started Kubernetes API Server.
Deploy ControllerManager
create profile
cd /opt/TLS/k8s/cfg
cat > kube-controller-manager.conf << EOF KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=false \\ --v=2 \\ --log-dir=/opt/kubernetes/logs \\ --leader-elect=true \\ --kubeconfig=/opt/kubernetes/cfg/kube-controller-manager.kubeconfig \\ --bind-address=127.0.0.1 \\ --allocate-node-cidrs=true \\ --cluster-cidr=10.244.0.0/16 \\ --service-cluster-ip-range=10.0.0.0/24 \\ --cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \\ --cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem \\ --root-ca-file=/opt/kubernetes/ssl/ca.pem \\ --service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem \\ --cluster-signing-duration=87600h0m0s" EOF
# • --kubeconfig: Connect apiserver The configuration file
# • --leader-elect: When the component starts more than one , Automatic election (HA)
# • --cluster-signing-cert-file/--cluster-signing-key-file: Automatically for kubelet Issued a certificate CA, And apiserver bring into correspondence with
Generate Certificate profile
cd /opt/TLS/k8s/ssl
cat > kube-controller-manager-csr.json << EOF { "CN": "system:kube-controller-manager", "hosts": [], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "L": "BeiJing", "ST": "BeiJing", "O": "system:masters", "OU": "System" } ] } EOF
Generate certificate file
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-controller-manager-csr.json | cfssljson -bare kube-controller-manager
....
[[email protected] ssl]# ll kube-controller-manager*
-rw-r--r-- 1 root root 1045 Apr 3 14:19 kube-controller-manager.csr
-rw-r--r-- 1 root root 255 Apr 3 14:18 kube-controller-manager-csr.json
-rw------- 1 root root 1679 Apr 3 14:19 kube-controller-manager-key.pem
-rw-r--r-- 1 root root 1436 Apr 3 14:19 kube-controller-manager.pem
# It's generated here kube-controller-manager.pem and kube-controller-manager-key.pem file
Generate kubeconfig file
# Set cluster parameters
kubectl config set-cluster kubernetes \
--certificate-authority=/opt/kubernetes/ssl/ca.pem \
--embed-certs=true \
--server=https://192.168.190.147:6443 \
--kubeconfig=/opt/TLS/k8s/cfg/kube-controller-manager.kubeconfig
# Set the client authentication parameters
kubectl config set-credentials kube-controller-manager \
--client-certificate=./kube-controller-manager.pem \
--client-key=./kube-controller-manager-key.pem \
--embed-certs=true \
--kubeconfig=/opt/TLS/k8s/cfg/kube-controller-manager.kubeconfig
# Setting context parameters
kubectl config set-context default \
--cluster=kubernetes \
--user=kube-controller-manager \
--kubeconfig=/opt/TLS/k8s/cfg/kube-controller-manager.kubeconfig
# Setting the default context
kubectl config use-context default --kubeconfig=/opt/TLS/k8s/cfg/kube-controller-manager.kubeconfig
Generate... File management
cd /opt/TLS/k8s/cfg
cat > kube-controller-manager.service << EOF [Unit] Description=Kubernetes Controller Manager Documentation=https://github.com/kubernetes/kubernetes [Service] EnvironmentFile=/opt/kubernetes/cfg/kube-controller-manager.conf ExecStart=/opt/kubernetes/bin/kube-controller-manager \$KUBE_CONTROLLER_MANAGER_OPTS Restart=on-failure [Install] WantedBy=multi-user.target EOF
Distribute documents
# Distribute certificate documents
scp -r /opt/TLS/k8s/ssl/kube-controller-manager*.pem /opt/kubernetes/ssl/
# Distribution profile
scp -r /opt/TLS/k8s/cfg/kube-controller-manager.conf /opt/kubernetes/cfg/
# Distribute management documents
scp /opt/TLS/k8s/cfg/kube-controller-manager.service /usr/lib/systemd/system/kube-controller-manager.service
# distribution kubeconfig file
scp /opt/TLS/k8s/cfg/kube-controller-manager.kubeconfig /opt/kubernetes/cfg/kube-controller-manager.kubeconfig
Check the documents
# Check the certificate file
[[email protected] cfg]# ll /opt/kubernetes/ssl/kube-controller-manager*.pem
-rw------- 1 root root 1679 Apr 3 14:30 /opt/kubernetes/ssl/kube-controller-manager-key.pem
-rw-r--r-- 1 root root 1436 Apr 3 14:30 /opt/kubernetes/ssl/kube-controller-manager.pem
# Check the configuration file
[[email protected] cfg]# ll /opt/kubernetes/cfg/kube-controller-manager.conf
-rw-r--r-- 1 root root 582 Apr 3 14:30 /opt/kubernetes/cfg/kube-controller-manager.conf
# Check the management documents
[[email protected] cfg]# ll /usr/lib/systemd/system/kube-controller-manager.service
-rw-r--r-- 1 root root 321 Apr 3 14:30 /usr/lib/systemd/system/kube-controller-manager.service
# check kubeconfig file
[[email protected] cfg]# ll /opt/kubernetes/cfg/kube-controller-manager.kubeconfig
-rw------- 1 root root 6279 Apr 3 14:30 /opt/kubernetes/cfg/kube-controller-manager.kubeconfig
start-up ControllerManager
[[email protected] cfg]# systemctl daemon-reload && systemctl start kube-controller-manager && systemctl enable kube-controller-manager && systemctl status kube-controller-manager
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-controller-manager.service to /usr/lib/systemd/system/kube-controller-manager.service.
● kube-controller-manager.service - Kubernetes Controller Manager
Loaded: loaded (/usr/lib/systemd/system/kube-controller-manager.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-04-03 14:33:09 CST; 111ms ago
Docs: https://github.com/kubernetes/kubernetes
Main PID: 11872 (kube-controller)
CGroup: /system.slice/kube-controller-manager.service
└─11872 /opt/kubernetes/bin/kube-controller-manager --logtostderr=false --v=2 --log-dir=/opt/kubernetes/logs --leader-elect=true --kubeconfig=/opt/kubernetes/cfg/kube-controller-manager.kubec...
Apr 03 14:33:09 k8s-master systemd[1]: Started Kubernetes Controller Manager.
Deploy Scheduler
Generate configuration files
cd /opt/TLS/k8s/cfg/
cat > kube-scheduler.conf << EOF KUBE_SCHEDULER_OPTS="--logtostderr=false \\ --v=2 \\ --log-dir=/opt/kubernetes/logs \\ --leader-elect \\ --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig \\ --bind-address=127.0.0.1" EOF
Generate Certificate profile
cd /opt/TLS/k8s/ssl
cat > kube-scheduler-csr.json << EOF { "CN": "system:kube-scheduler", "hosts": [], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "L": "BeiJing", "ST": "BeiJing", "O": "system:masters", "OU": "System" } ] } EOF
Generate certificate file
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-scheduler-csr.json | cfssljson -bare kube-scheduler
[roo[email protected] ssl]# ll kube-scheduler*
-rw-r--r-- 1 root root 1029 Apr 3 14:37 kube-scheduler.csr
-rw-r--r-- 1 root root 245 Apr 3 14:37 kube-scheduler-csr.json
-rw------- 1 root root 1675 Apr 3 14:37 kube-scheduler-key.pem
-rw-r--r-- 1 root root 1424 Apr 3 14:37 kube-scheduler.pem
# It's generated here kube-scheduler.pem and kube-scheduler-key.pem file
Generate kubeconfig file
# Set cluster parameters
kubectl config set-cluster kubernetes \
--certificate-authority=/opt/kubernetes/ssl/ca.pem \
--embed-certs=true \
--server=https://192.168.190.147:6443 \
--kubeconfig=/opt/TLS/k8s/cfg/kube-scheduler.kubeconfig
# Set the client authentication parameters
kubectl config set-credentials kube-scheduler \
--client-certificate=./kube-scheduler.pem \
--client-key=./kube-scheduler-key.pem \
--embed-certs=true \
--kubeconfig=/opt/TLS/k8s/cfg/kube-scheduler.kubeconfig
# Setting context parameters
kubectl config set-context default \
--cluster=kubernetes \
--user=kube-scheduler \
--kubeconfig=/opt/TLS/k8s/cfg/kube-scheduler.kubeconfig
# Setting the default context
kubectl config use-context default --kubeconfig=/opt/TLS/k8s/cfg/kube-scheduler.kubeconfig
Generate... File management
cd /opt/TLS/k8s/cfg
cat > kube-scheduler.service << EOF [Unit] Description=Kubernetes Scheduler Documentation=https://github.com/kubernetes/kubernetes [Service] EnvironmentFile=/opt/kubernetes/cfg/kube-scheduler.conf ExecStart=/opt/kubernetes/bin/kube-scheduler \$KUBE_SCHEDULER_OPTS Restart=on-failure [Install] WantedBy=multi-user.target EOF
Distribute documents
# Distribution profile
scp /opt/TLS/k8s/cfg/kube-scheduler.conf /opt/kubernetes/cfg/kube-scheduler.conf
# Distribute certificate documents
scp /opt/TLS/k8s/ssl/kube-scheduler*.pem /opt/kubernetes/ssl/
# distribution kubeconfig file
scp /opt/TLS/k8s/cfg/kube-scheduler.kubeconfig /opt/kubernetes/cfg/kube-scheduler.kubeconfig
# Distribute management documents
scp /opt/TLS/k8s/cfg/kube-scheduler.service /usr/lib/systemd/system/kube-scheduler.service
Check the documents
# Check the configuration file
[[email protected] cfg]# ll /opt/kubernetes/cfg/kube-scheduler.conf
-rw-r--r-- 1 root root 188 Apr 3 14:44 /opt/kubernetes/cfg/kube-scheduler.conf
# Check the certificate file
[[email protected] cfg]# ll /opt/kubernetes/ssl/kube-scheduler*.pem
-rw------- 1 root root 1675 Apr 3 14:45 /opt/kubernetes/ssl/kube-scheduler-key.pem
-rw-r--r-- 1 root root 1424 Apr 3 14:45 /opt/kubernetes/ssl/kube-scheduler.pem
# check kubeconfig file
[[email protected] cfg]# ll /opt/kubernetes/cfg/kube-scheduler.kubeconfig
-rw------- 1 root root 6241 Apr 3 14:45 /opt/kubernetes/cfg/kube-scheduler.kubeconfig
# Check the management documents
[[email protected] cfg]# ll /usr/lib/systemd/system/kube-scheduler.service
-rw-r--r-- 1 root root 285 Apr 3 14:45 /usr/lib/systemd/system/kube-scheduler.service
start-up schedule
systemctl daemon-reload && systemctl start kube-scheduler && systemctl enable kube-scheduler && systemctl status kube-scheduler
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-scheduler.service to /usr/lib/systemd/system/kube-scheduler.service.
● kube-scheduler.service - Kubernetes Scheduler
Loaded: loaded (/usr/lib/systemd/system/kube-scheduler.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-04-03 14:48:19 CST; 113ms ago
Docs: https://github.com/kubernetes/kubernetes
Main PID: 11972 (kube-scheduler)
CGroup: /system.slice/kube-scheduler.service
└─11972 /opt/kubernetes/bin/kube-scheduler --logtostderr=false --v=2 --log-dir=/opt/kubernetes/logs --leader-elect --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig --bind-address=12...
Apr 03 14:48:19 vm01 systemd[1]: Started Kubernetes Scheduler.
Apr 03 14:48:19 vm01 kube-scheduler[11972]: Flag --logtostderr has been deprecated, will be removed in a future release, see https://github.com/kubernetes/enhancements/tree/master/keps/sig...k8s-components
Apr 03 14:48:19 vm01 kube-scheduler[11972]: Flag --log-dir has been deprecated, will be removed in a future release, see https://github.com/kubernetes/enhancements/tree/master/keps/sig-ins...k8s-components
Hint: Some lines were ellipsized, use -l to show in full.
thus ,Master Three components on the node (Apiserver、ControllerManager、Scheduler) Deployed and started successfully .
边栏推荐
- [detailed explanation of kubernetes 12] - Security Certification
- Five highlights of wwdc2022 lock screen, weather kit, swiftui, collaboration function, apple payment
- 故障分析 | MySQL 中新建用户无法登陆的一种特殊场景
- Free video format converter
- The easynvr hardware of the video edge computing gateway always reports an error when it is started in the service mode. How to troubleshoot and solve it?
- This book has won the 2022 Beijing college entrance examination composition!
- Laravel determines whether the mailbox already exists and verifies whether the mailbox format is legal
- ArcGIS Runtime 离线gdb数据缺失问题处理
- word+正则表达式==快速批量添加图注题注(保姆级图文)
- [machinetranslation] a training of multilingual machinetranslation model
猜你喜欢
![[leetcode hash + Moore voting] 169 Most elements 229 Majority Element II](/img/07/f632d472f292e3914d78c62e7fb9b6.png)
[leetcode hash + Moore voting] 169 Most elements 229 Majority Element II

Tamidog information | Maersk completed another large-scale enterprise acquisition

服务器注册使用

Why common read SQL is sent to the master instance in the distributed dble read / write separation scenario

Simple use of Wireshark

Fault analysis how the MySQL database gets stuck after upgrading

Please ask about the SQL injection problem

Word+ regular expression = = quickly batch add caption (nanny level text)

神经网络学习(四)----神经网络各层知识的简单总结

Customized development of blind box app system
随机推荐
HLS 直播协议m3u8详解
Free video format converter
Implementing parallel computing framework with QT
Opencv learning notes 1
Simple use of Wireshark
Five highlights of wwdc2022 lock screen, weather kit, swiftui, collaboration function, apple payment
Redis the distance between two points and the center point
Concurrent operation -- reentrantreadwritelock
网页设计期末大作业-景点旅游网站(含导航栏,轮播图,样式精美)
Octopus network louis:gamefi as an application chain has gradually become a consensus
No cached version available for offline mode
Why common read SQL is sent to the master instance in the distributed dble read / write separation scenario
No cached version available for offline mode
Server registration use
关于我的那些事【我的2022】
2022年短期理财产品排行榜
C#/VB. Net to set solid color / gradient / picture background in word
月薪近万,3年销售助理转行测试,0经验的我如何拿到多份offer?
Electron desktop development (process)
控制台输入命令 net start mysql 控制台输出系统发生错误 5。 拒绝访问。MySQL 服务正在启动.MySQL 服务无法启动。服务没有报告任何错误。请键入 NET HELPMSG 353