1、所有机器添加master域名映射，以下IP和节点名字需要修改为自己的
ip addr查看
[root@cluster-master ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:74:ad:ef brd ff:ff:ff:ff:ff:ff
inet 192.76.116.201/24 brd 192.76.116.255 scope global noprefixroute ens33 # 这里就是本机的IP
valid_lft forever preferred_lft forever
inet6 fe80::633a:110a:7f35:2713/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:f0:76:df:55 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 # 这里是给docker分的IP
valid_lft forever preferred_lft forever
每个节点都执行
echo "192.76.116.201 cluster-endpoint" >> /etc/hosts
2、主节点初始化（只在主节点运行！！！）
kubeadm init \
--apiserver-advertise-address=192.76.116.201 \ # master节点的IP
--control-plane-endpoint=cluster-endpoint \
--image-repository registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images \
--kubernetes-version v1.20.9 \
--service-cidr=10.96.0.0/16 \ # 不用改
--pod-network-cidr=192.168.0.0/16 # 最好不改
无注释版
kubeadm init \
--apiserver-advertise-address=192.76.116.201 \
--control-plane-endpoint=cluster-endpoint \
--image-repository registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images \
--kubernetes-version v1.20.9 \
--service-cidr=10.96.0.0/16 \
--pod-network-cidr=192.168.0.0/16
#所有网络范围不重叠
3、复制保留之后出来的界面的信息（含有token和提示添加pod网络的信息）
Your Kubernetes control-plane 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
Alternatively, if you are the root user, you can run:
export KUBECONFIG=/etc/kubernetes/admin.conf
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/
# 加入master节点
You can now join any number of control-plane nodes by copying certificate authorities
and service account keys on each node and then running the following as root:
kubeadm join cluster-endpoint:6443 --token ls3xy7.7cl3pv1paz0tgzx3 \
--discovery-token-ca-cert-hash sha256:c676fa63e72c118635cef85d137ae7f93c2d3ca21d67b79c3ba2f4bbb5aec90f \
--control-plane
# 加入worker节点
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join cluster-endpoint:6443 --token ls3xy7.7cl3pv1paz0tgzx3 \
--discovery-token-ca-cert-hash sha256:c676fa63e72c118635cef85d137ae7f93c2d3ca21d67b79c3ba2f4bbb5aec90f
关闭一下防火墙：systemctl disable firewalld --now
curl https://docs.projectcalico.org/manifests/calico.yaml -O
用下面这个，上面的可能大概也许会因为版本问题报错
curl https://docs.projectcalico.org/v3.20/manifests/calico.yaml -O
cat calico.yaml |grep 192.168 # 查看配置文件这个信息，如果之前在第二步初始化主节点的时候修改过，这里要改成对应的IP
有信息再使用下面这个
kubectl apply -f calico.yaml
：cat搜索之后不显示，或者curl: (35) Encountered end of file
：关闭一下防火墙：systemctl disable firewalld --now
：
：参考https://blog.csdn.net/qq_46237746/article/details/125453966
查看K8S版本
[root@cluster-master ~]# kubectl version
Client Version: version.Info{
Major:"1", Minor:"20", GitVersion:"v1.20.9", GitCommit:"7a576bc3935a6b555e33346fd73ad77c925e9e4a",GitTreeState:"clean", BuildDate:"2021-07-15T21:01:38Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{
Major:"1", Minor:"20", GitVersion:"v1.20.9", GitCommit:"7a576bc3935a6b555e33346fd73ad77c925e9e4a",GitTreeState:"clean", BuildDate:"2021-07-15T20:56:38Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}
修改yaml文件参考https://blog.csdn.net/moyuanbomo/article/details/123092448，文末也有
：报错Init:0/3
：镜像版本不一致
参考文章CSDN博客 https://blog.csdn.net/cuichongxin/article/details/121615068
：
[root@cluster-master ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
cluster-master Ready control-plane,master 161m v1.20.9
kubectl get pods -A
使用第二步得到的信息，join worker的信息，在node1和node2上运行
kubeadm join cluster-endpoint:6443 --token ls3xy7.7cl3pv1paz0tgzx3 \
--discovery-token-ca-cert-hash sha256:c676fa63e72c118635cef85d137ae7f93c2d3ca21d67b79c3ba2f4bbb5aec90f
如果令牌过期了，键入以下命令
kubeadm token create --print-join-command
再使用kubectl get nodes即可查看，当然这需要等一等
kubectl get pods -A
：[ERROR FileContent–proc-sys-net-ipv4-ip_forward]: /proc/sys/net/ipv4/ip_forward contents are not set to 1
：这个是因为安装master节点时环境准备没有做好：按照下列操作
cat > /etc/sysctl.d/k8s.conf << EOF net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-iptables=1 net.bridge.bridge-nf-call-ip6tables=1 net.ipv4.ip_forward=1 net.ipv4.tcp_tw_recycle=0 vm.swappiness=0 vm.overcommit_memory=1 vm.panic_on_oom=0 fs.inotify.max_user_instances=8192 fs.inotify.max_user_watches=1048576 fs.file-max=52706963 fs.nr_open=52706963 net.ipv6.conf.all.disable_ipv6=1 net.netfilter.nf_conntrack_max=2310720 EOF
sysctl --system
成功加入集群
查看主节点的nodes和pods
很慢很慢很慢！！！时刻在变化
参考：Kubernetes Pod 提示 ： Init:ImagePullBackOff_WANGMCHAO的博客-CSDN博客
：
一直PodInitializing
：
kubectl describe pod calico-node-sn7d7 --namespace=kube-system 查看为啥
手动的拉去下载不下来的镜像
再来
全部Ready
1、kubectl apply命令，根据配置文件里面列出来的内容，升级现有的
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.3.1/aio/deploy/recommended.yaml
2、设置访问端口 把type: ClusterIP 改为 type: NodePort
kubectl edit svc kubernetes-dashboard -n kubernetes-dashboard
3、显示到端口，在安全组放行
kubectl get svc -A |grep kubernetes-dashboard
访问一下https://ip:端口，出来界面，这个IP端口写工作节点的IP（我试了好久master节点的，不能成功访问）
一定要注意，如果是单机版，则直接master-ip:port即可以访问，如果是云版本，一定到找到pod对应的node，然后浏览器访问 node-ip:port访问。
：Dashboard的pod状态为CrashLoopBackOff
：kubernetes(k8s)创建Dashboard失败，Dashboard的pod状态为CrashLoopBackOff 解决方法 - 知乎 (zhihu.com)
：
删除dashboard，好像删不干净，每次apply dashboard的时候会有unchanged的信息，那些就是没删干净的，不过好像不影响，主要是要修改yaml，重新apply
kubectl delete -f dashboard.yaml
kubectl get deployment --all-namespaces
kubectl -n kubernetes-dashboard delete $(sudo kubectl -n kubernetes-dashboard get deployment -o name | grep dashboard)
1、访问这个网页复制页面yaml：https://raw.githubusercontent.com/kubernetes/dashboard/v2.3.1/aio/deploy/recommended.yaml
文末也有这个文件
vi dashboard.yaml 输入yaml
2、拉取镜像
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1
3、创建服务
kubectl apply -f dashboard.yaml
4、查看pods状态
kubectl get pods -A
下面这两个是running即可
kubernetes-dashboard dashboard-metrics-scraper-79c5968bdc-sqs8f 1/1 Running 1 11h
kubernetes-dashboard kubernetes-dashboard-658485d5c7-fctq4 1/1 Running 14 11h
5、查看暴露的端口
[root@cluster-master ~]# kubectl get pods,svc -n kubernetes-dashboard
NAME READY STATUS RESTARTS AGE
pod/dashboard-metrics-scraper-79c5968bdc-sqs8f 1/1 Running 1 11h
pod/kubernetes-dashboard-658485d5c7-fctq4 1/1 Running 14 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/dashboard-metrics-scraper ClusterIP 10.96.199.85 <none> 8000/TCP 11h
service/kubernetes-dashboard NodePort 10.96.96.225 <none> 443:30558/TCP 25m
6、访问https://cluster-node1的IP:30558 即 https://192.76.116.202:30558
点“高级”继续访问
[root@cluster-master ~]# kubectl create serviceaccount dashboard-admin -n kube-system
serviceaccount/dashboard-admin created
[root@cluster-master ~]# kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin created
[root@cluster-master ~]# kubectl describe secrets -n kube-system $(kubectl -n kube-system get secret | awk '/dashboard-admin/{print $1}')
Name: dashboard-admin-token-zgdbv
Namespace: kube-system
Labels: <none>
Annotations: kubernetes.io/service-account.name: dashboard-admin
kubernetes.io/service-account.uid: cffacd35-9cef-40e9-8b43-c2c3009de5d7
Type: kubernetes.io/service-account-token
Data
====
token: eyJhbGciOiJSUzI1NiIsImtpZCI6IkVqNWhvN2MxT2VTTjRPY1I5ZlVjUTcyUXBMeDg3SDQzZnJVdDUtYkRRaVUifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4temdkYnYiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWluIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiY2ZmYWNkMzUtOWNlZi00MGU5LThiNDMtYzJjMzAwOWRlNWQ3Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRhc2hib2FyZC1hZG1pbiJ9.keo3Ryr8uHPCkUDCJBuF_XTTz0SNunVg5rtyDOA0aJOdL1NDCWcKn75aa-ceHvuotRDeLIQ5Yn61Frflu7-foGzaQU2ozyaOCrElukvr3cMA-UXLi1Vzoc39uWAfZBB7z6gAxGUqUBtw53CqXgS668gIAthPYlK8FWwjwGBBbF7zR6YYO3vbEWChJmXGjXBlAht2va36EBYOjzA2liHFLBefCEwB5dBF3Pq-OqVYGn6nKHq29o8siFAMEGGTOna9x3URFzLDsTLnX6qHEHJ4zZtM6SvISs7r569pPDKukCiJeZqhstXRb7cVuXNG8sty-xDK8q58cc732yB8iJH9Pg
ca.crt: 1066 bytes
namespace: 11 bytes
另外一个生成token的方法是这个，我没测试过：
-- 1、创建访问账号，准备一个yaml文件； vi dash.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: admin-user
namespace: kubernetes-dashboard
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: admin-user
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: admin-user
namespace: kubernetes-dashboard
-- 2、apply一下
kubectl apply -f dash.yaml
令牌访问
#获取访问令牌
kubectl -n kubernetes-dashboard get secret $(kubectl -n kubernetes-dashboard get sa/admin-user -o jsonpath="{
.secrets[0].name}") -o go-template="{
{
.data.token | base64decode}}"
得到的令牌：
每个Pod - k8s都会分配一个ip，我们这里是192.168.191.196 这个子网是在我们之前4.2.2的时候主节点初始化（只在主节点运行！！！）的时候配置的哟，记得吧，另外默认的也是这个网段
# 查看Pod的运行日志
不需要加pod 因为只有pod有日志
logs -f 可以追踪
kubectl logs Pod名字
# 每个Pod - k8s都会分配一个ip
kubectl get pod -o wide
# 使用Pod的ip+pod里面运行容器的端口
[root@cluster-master ~]# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
myapp 2/2 Running 0 6m 192.168.191.196 cluster-node2 <none> <none>
[root@cluster-master ~]# curl 192.168.191.196
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html {
color-scheme: light dark; }
body {
width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
# 集群中的任意一个机器以及任意的应用都能通过Pod分配的ip来访问这个Pod
k8s会，那么整个集群里的机器就可以通过这个IP来访问这个Pod里的容器，
Pod里的容器是可以互通的，因为，所以使用127.0.0.1访问即可
# 进入Pod里默认的mynginx容器
[root@cluster-master ~]# kubectl exec -it myapp -- /bin/bash
Defaulting container name to mynginx.
Use 'kubectl describe pod/myapp -n default' to see all of the containers in this pod.
# 测试访问mynginx Success
root@myapp:/# curl 127.0.0.1
xiaowei coming here!
# 测试访问mytomcat Success
root@myapp:/# curl 127.0.0.1:8080
<!doctype html><html lang="en"><head><title>HTTP Status 404 ? Not Found</title><style type="text/css">body {
font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {
color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 ? Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat/9.0.56</h3></body></html>
：
