kubernetes(六) 基于kubeadm构建高可用k8s集群
基于kubeadm构建高可用k8s集群
github地址： https://github.com/kubernetes/kubernetes/
官方网站： kubernets.io
基于kubeadm创建k8s集群
基础概念
pod使用接口技术
- CNI： container network interface
- CSI： container storage interface
- CRI： container runtime interface
- CVI： container volume interface
pod：k8s中运行容器的最小单元
- k8s如果向替换CRI的话（替换容器技术），只需要讲POD使用相关的容器技术（docker，podman）封装即可
service： 实现了从宿主机外层访问k8s内部不同的容器的访问方式，还实现了pod的动态发现；因此可以说Service是k8s内部的负载均衡器
- 实现方式： 早期是iptable，在1.11之后支持ipvs（轮训算法）
- replicationcontroller/deployment： 已废弃,POD控制器； 通过环境检测，保证pod的正常运行
k8s组成部分介绍
master： 主节点
- kube-apiserver： https://k8smeetup.github.io/docs/admin/kube-apiserver/
- 为api对象验证并配置数据，包括pods，services，APIserver提供Restful操作和到集群共享状态的前端，所有其它组件通过apiserver进行交互
- kube-scheduler：https://k8smeetup.github.io/docs/admin/kube-scheduler/
- 具有丰富的资源策略，能够感知拓扑变化，支持特定负载的功能组件，它对集群的可用性，性能表现以及容量都影响巨大，scheduler需要考虑独立的和集体的资源需求，服务质量需求，硬件、软件，策略限制，亲和与反亲和规范，数据位置吗内部负载接口，截止时间等等，如有特定的负载需求可以通过apiserver暴露出来
- kube-controller-manager: https://k8smeetup.github.io/docs/admin/kube-controller-manager/
- 作为集群内部的控制中心，负责集群内部的Node，Pod副本，服务端点，命名空间，服务账号，资源配额的管理，当某个Node意外宕机时，controller-manager会及时发现并执行自动修复，确保集群始终处于预期的工作状态
- kube-apiserver： https://k8smeetup.github.io/docs/admin/kube-apiserver/
Node节点
kube-proxy： https://k8smeetup.github.io/docs/admin/kube-proxy/
维护node节点上的网络规则，实现用户访问请求的转发，其实就是转发给service，需要管理员指定service和NodePort的对应关系
- Kubernetes 网络代理运行在 node 上。它反映了 node 上 Kubernetes API 中定义的服务，并可以通过一组后端进行简单的 TCP、UDP 流转发或循环模式（round robin)）的 TCP、UDP 转发。目前，服务的集群 IP 和端口是通过 Docker-links 兼容的环境变量发现的，这些环境变量指定了服务代码打开的端口。有一个可选的 addon 为这些集群 IP 提供集群 DNS。用户必须使用 apiserver API 创建一个服务来配置代理。
- kubelet： https://k8smeetup.github.io/docs/admin/kubelet/
- kubelet 是运行在每个节点上的主要的“节点代理”，它按照 PodSpec 中的描述工作。 PodSpec 是用来描述一个 pod 的 YAML 或者 JSON 对象。kubelet 通过各种机制（主要通过 apiserver ）获取一组 PodSpec 并保证在这些 PodSpec 中描述的容器健康运行。kubelet 不管理不是由 Kubernetes 创建的容器。
- 除了来自 apiserver 的 PodSpec ，还有 3 种方式可以将容器清单提供给 kubelet 。
- 文件：在命令行指定的一个路径，在这个路径下的文件将被周期性的监视更新，默认监视周期是 20 秒并可以通过参数配置。
- HTTP端点：在命令行指定的一个HTTP端点，该端点每 20 秒被检查一次并且可以通过参数配置检查周期。
- HTTP服务：kubelet 还可以监听 HTTP 服务并响应一个简单的 API 来创建一个新的清单
- ETCD： 存储所有集群数据
组件官网参考： https://kubernetes.io/zh/docs/concepts/overview/components/
部署k8s集群
集群规划
| 角色 | 主机名 | ip地址 | 软件 |
|---|---|---|---|
| master-1 | centos7-node1 | 192.168.56.11 | docker,kube-comtroller-manager,kube-apiserver,kube-schduler |
| master-2 | centos7-node2 | 192.168.56.12 | docker,kube-comtroller-manager,kube-apiserver,kube-schduler |
| master-3 | centos7-node3 | 192.168.56.13 | docker,kube-comtroller-manager,kube-apiserver,kube-schduler |
| ha-1 | centos7-node4 | 192.168.56.14 | haproxy,keepalived |
| ha-2 | centos7-node5 | 192.168.56.15 | haproxy,keepalived |
| harbor-1 | centos7-node6 | 192.168.56.16 | docker,docker-compose,harbor |
| node-1 | centos7-node7 | 192.168.56.17 | kubelet,kube-proxy |
| node-2 | centos7-node8 | 192.168.56.18 | kubelet,kube-proxy |
基础环境准备
- 服务器使用centos7.6以及以上,配置阿里云仓库
$ wget -O /etc/yum.repos.d/CentOS-Base.repo https://mirrors.aliyun.com/repo/Centos-7.repo && yum -y install epel-release $ wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker.repo
- 关闭防火墙&selinux&swap
$ sed -i ‘/SELINUX=enforcing/SELINUX=disable/g‘ /etc/selinux/config $ systemctl stop firewalld && systemctl disable firewalld $ sed -i ‘/swap/s/^\(.*\)$/#\1/g‘ /etc/fstab $ swapoff -a
- 自动更新时间
$ yum install chrony -y && systemctl enable chronyd && systemctl start chronyd && timedatectl set-timezone Asia/Shanghai && timedatectl set-ntp yes
- 设置主机名&hosts解析
$ cat /etc/hosts 192.168.56.11 centos7-node1 192.168.56.12 centos7-node2 192.168.56.13 centos7-node3 192.168.56.14 centos7-node4 192.168.56.15 centos7-node5 192.168.56.16 centos7-node6 192.168.56.17 centos7-node7 192.168.56.18 centos7-node8 192.168.56.16 harbor.magedu.com
- 系统参数优化(ip地址转发)
$ modprobe br_netfilter $modprobe br_netfilter && cat > /etc/sysctl.d/k8s.conf << EOF net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 net.ipv4.ip_forward = 1 EOF sysctl -p /etc/sysctl.d/k8s.conf
- 开启ipvs
yum -y install ipvsadm ipset cat > /etc/sysconfig/modules/ipvs.modules <<EOF modprobe -- ip_vs modprobe -- ip_vs_rr modprobe -- ip_vs_wrr modprobe -- ip_vs_sh modprobe -- nf_conntrack_ipv4 EOF
- 重启服务器
- 基础docker安装
$mkdir -p /etc/docker && yum -y install docker-ce
$ tee /etc/docker/daemon.json <<-‘EOF‘
{
"registry-mirrors": ["https://0b8hhs68.mirror.aliyuncs.com"],
"insecure-registry": ["harbor.magedu.com"],
"exec-opts": ["native.cgroupdriver=systemd"]
}
EOF
$ systemctl enable docker && systemctl start docker部署harbor与haproxy反向代理
- harbor
$ yum -y install epel-release docker-compose $ wget https://github.com/goharbor/harbor/releases/download/v2.0.0/harbor-offline-installer-v2.0.0.tgz $ tar xf harbor-offline-installer-v2.0.0.tgz -C /usr/local/src && cd /usr/local/src/harbor $ cp harbor.yml.tmpl harbor.yml $ vim harbor.yml hostname: harbor.magedu.com http: # port for http, default is 80. If https enabled, this port will redirect to https port port: 80 # https related config #https: # https port for harbor, default is 443 # port: 443 # The path of cert and key files for nginx # certificate: /your/certificate/path # private_key: /your/private/key/path $ ./install.sh
创建baseimages镜像仓库
- haproxy&keepalived
$ yum -y install keepalived haproxy
$ vim /etc/keepalived/keepalived.conf
! Configuration File for keepalived
global_defs {
notification_email {
}
notification_email_from
smtp_server 192.168.200.1
smtp_connect_timeout 30
router_id LVS_DEVEL
vrrp_skip_check_adv_addr
vrrp_strict
vrrp_garp_interval 0
vrrp_gna_interval 0
}
vrrp_instance VI_1 {
state MASTER
interface ens33
virtual_router_id 56
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.56.110 dev ens33 label ens33:1
}
}
$ systemctl enable keepalived && systemctl start keepalived
$ vim /etc/haproxy/haproxy.cfg
listen k8s-api-6443
bind 192.168.56.110:6443
mode tcp
server centos7-node1 192.168.56.11:6443 check inter 3s fall 3 rise 5
server centos7-node2 192.168.56.12:6443 check inter 3s fall 3 rise 5
server centos7-node3 192.168.56.13:6443 check inter 3s fall 3 rise 5
$ systemctl restart haproxy
$ ss -tnl | grep 6443 # 测试存活node节点和master节点部署
- master节点安装
$ cat <<EOF > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=kubernetes baseurl=https://mirrors.tuna.tsinghua.edu.cn/kubernetes/yum/repos/kubernetes-el7-$basearch enabled=1 EOF $ yum install -y kubelet-1.17.2 kubeadm-1.17.2 kubectl-1.17.2 $ systemctl enable kubelet && systemctl start kubelet
master节点初始化集群
- 开启 master命令补全
$ mkdir /data/scripts -p $ kubeadm completion bash > /data/scripts/kubeadm_completion.sh && chmod +x /data/scripts/kubeadm_completion.sh $ vim /etc/profile source /data/scripts/kubeadm_completion.sh $ source /etc/profile $ kubeadm config print default #打印默认初始化配置 $ kubeadm config images list --kubernetes-version v1.17.2 # 打印需要下载的软件 $ kubeadm init --apiserver-advertise-address=192.168.56.11 --apiserver-bind-port=6443 --control-plane-endpoint=192.168.56.110 --kubernetes-version=v1.17.2 --ignore-preflight-errors=swap --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --pod-network-cidr=10.10.0.0/16 --service-cidr=172.26.0.0/16 --service-dns-domain=linux.local #记住返回的信息 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 192.168.56.14:6443 --token iou3pg.8q2f13dbw8z2l4lm --discovery-token-ca-cert-hash sha256:e13d02eea0bd631ba8cae228a31b3cc783686544761de1b3c4d514f313f501c3 --control-plane Then you can join any number of worker nodes by running the following on each as root: kubeadm join 192.168.56.14:6443 --token iou3pg.8q2f13dbw8z2l4lm --discovery-token-ca-cert-hash sha256:e13d02eea0bd631ba8cae228a31b3cc783686544761de1b3c4d514f313f501c3 $ kubeadm init phase upload-certs --upload-certs #生成controplane信息 6c3a44aee4b3fabb5beb44ab696fee6043c77d3461cee1f2c9e80058aa42d493 #### 需要在其他两个master节点执行 $ kubeadm join 192.168.56.14:6443 --token iou3pg.8q2f13dbw8z2l4lm --discovery-token-ca-cert-hash sha256:e13d02eea0bd631ba8cae228a31b3cc783686544761de1b3c4d514f313f501c3 --control-plane --certificate-key 6c3a44aee4b3fabb5beb44ab696fee6043c77d3461cee1f2c9e80058aa42d493 $ kubectl get nodes #状态不ok。需要安装网络插件 NAME STATUS ROLES AGE VERSION centos7-node1 NotReady master 37m v1.17.2 centos7-node2 NotReady master 25m v1.17.2 centos7-node3 NotReady master 18m v1.17.2
- 通过配置文件初始化master
$ cat kubeadm-1.17.2.yml
apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
- system:bootstrappers:kubeadm:default-node-token
token: abcdef.0123456789abcdef
ttl: 48h0m0s
usages:
- signing
- authentication
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.56.11
bindPort: 6443
nodeRegistration:
criSocket: /var/run/dockershim.sock
name: centos7-node1
taints:
- effect: NoSchedule
key: node-role.kubernetes.io/master
---
apiServer:
timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controlPlaneEndpoint: 192.168.56.110
controllerManager: {}
dns:
type: CoreDNS
etcd:
local:
dataDir: /var/lib/etcd
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers
kind: ClusterConfiguration
kubernetesVersion: v1.17.2
networking:
dnsDomain: linux.local
podSubnet: 10.10.0.0/16
serviceSubnet: 172.26.0.0/16
scheduler: {}
$ kubeadm init --config kubeadm-1.17.2.yml #其中一个master上一次，然后重新加入其他master节点即可验证集群状态
- 安装网络插件flannel
$ vim /etc/hosts
# GitHub Start
52.74.223.119 github.com
192.30.253.119 gist.github.com
54.169.195.247 api.github.com
185.199.111.153 assets-cdn.github.com
151.101.76.133 raw.githubusercontent.com
151.101.76.133 gist.githubusercontent.com
151.101.76.133 cloud.githubusercontent.com
151.101.76.133 camo.githubusercontent.com
151.101.76.133 avatars0.githubusercontent.com
151.101.76.133 avatars1.githubusercontent.com
151.101.76.133 avatars2.githubusercontent.com
151.101.76.133 avatars3.githubusercontent.com
151.101.76.133 avatars4.githubusercontent.com
151.101.76.133 avatars5.githubusercontent.com
151.101.76.133 avatars6.githubusercontent.com
151.101.76.133 avatars7.githubusercontent.com
151.101.76.133 avatars8.githubusercontent.com
# GitHub End
$ wget wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
$ vim kube-flannel.yml #子网与service一致
net-conf.json: |
{
"Network": "10.10.0.0/16",
"Backend": {
"Type": "vxlan"
}
}
$ kubectl apply -f kube-flannel.yml
$ kubectl get nodes #master状态全部Ready
NAME STATUS ROLES AGE VERSION
centos7-node1 Ready master 38m v1.17.2
centos7-node2 Ready master 26m v1.17.2
centos7-node3 Ready master 19m v1.17.2验证node节点状态
$ cat <<EOF > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=kubernetes baseurl=https://mirrors.tuna.tsinghua.edu.cn/kubernetes/yum/repos/kubernetes-el7-$basearch enabled=1 EOF $ yum install -y kubelet-1.17.2 kubeadm-1.17.2 $ systemctl enable kubelet && systemctl start kubelet
node节点加入master
$ kubeadm join 192.168.56.14:6443 --token iou3pg.8q2f13dbw8z2l4lm --discovery-token-ca-cert-hash sha256:e13d02eea0bd631ba8cae228a31b3cc783686544761de1b3c4d514f313f501c3
创建POD测试网络环境
- 创建kubernetes的流程： https://k8smeetup.github.io/docs/reference/setup-tools/kubeadm/kubeadm-init/#init-workflow
$ kubectl run net-test1 --image=alpine --replicas=3 sleep 360000 #创建测试 $ kubectl run net-test2 --image=alpine --replicas=3 sleep 360000 $ kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES net-test1 1/1 Running 1 17h 10.10.5.3 centos7-node8 <none> <none> net-test2 1/1 Running 1 17h 10.10.3.3 centos7-node7 <none> <none> / # ping -c 3 qq.com # 外网测试 PING qq.com (58.250.137.36): 56 data bytes 64 bytes from 58.250.137.36: seq=0 ttl=127 time=42.395 ms 64 bytes from 58.250.137.36: seq=1 ttl=127 time=42.930 ms 64 bytes from 58.250.137.36: seq=2 ttl=127 time=42.146 ms / # ping -c 3 192.168.56.13 #宿主机测试 PING 192.168.56.13 (192.168.56.13): 56 data bytes 64 bytes from 192.168.56.13: seq=0 ttl=63 time=0.438 ms 64 bytes from 192.168.56.13: seq=1 ttl=63 time=0.468 ms / # ping -c 3 10.10.3.3 #pod间测试 PING 10.10.3.3 (10.10.3.3): 56 data bytes 64 bytes from 10.10.3.3: seq=0 ttl=62 time=1.153 ms 64 bytes from 10.10.3.3: seq=1 ttl=62 time=1.069 ms 64 bytes from 10.10.3.3: seq=2 ttl=62 time=1.296 ms
部署web服务Dashboard
- 使用2.0.0-rc6版本
$ docker pull kubernetesui/dashboard:v2.0.0-rc6
$ docker pull kubernetesui/metrics-scraper:v1.0.3
$ docker tag kubernetesui/dashboard:v2.0.0-rc6 harbor.magedu.com/baseimages/dashboard:v2.0.0-rc6
$ docker tag 3327f0dbcb4a harbor.magedu.com/baseimages/metrics-scraper:v1.0.3 #根据tag打镜像
$ docker login
$ docker push harbor.magedu.com/baseimages/dashboard:v2.0.0-rc6
$ docker push harbor.magedu.com/baseimages/metrics-scraper:v1.0.3
# 修改配置
$ wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc6/aio/deploy/recommended.yaml
$ vim dashboard-2.0.0-rc6.yml #新增service的端口暴露与内网harbor
image: harbor.magedu.com/baseimages/dashboard:v2.0.0-rc6 #两处修改
image: harbor.magedu.com/baseimages/metrics-scraper:v1.0.3 #两处修改
kind: Service
apiVersion: v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kubernetes-dashboard
spec:
type: NodePort
ports:
- port: 443
targetPort: 8443
nodePort: 30002
selector:
k8s-app: kubernetes-dashboard
$ vim admin-user.yml
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
$ kubectl apply -f dashboard-2.0.0-rc6.yml
$ kubectl apply -f admin-user.yml
$ kubectl get pod -A
$ kubectl get svc -A访问任意主机的https://192.168.56.12:30002 即可
- 获取访问token即可登陆
$ kubectl get secret -A | grep admin-user kubernetes-dashboard admin-user-token-5vvwn kubernetes.io/service-account-token 3 6m17s $ kubectl describe secret admin-user-token-5vvwn -n kubernetes-dashboard 获取token即可
k8s集群升级
- 升级时间： 业务低峰期
- 升级方式
- ansible
- kubeadm
kubeadm升级方式
升级步骤
- 在所有master节点进行升级，升级管理断服务kube-controller-manager,kube-apiserver,kube-scheduler,kube-proxy
- 检查可升级的软件版本
$ yum list --showduplicates | grep kubeadm $ yum -y install kubeadm-1.17.4 $ kubeadm upgrade plan #检查升级计划
- 所有master节点都安装1.17.4的kubeadm
$ yum -y install kubeadm-1.17.4 $ kubeadm upgrade apply v1.17.4
- 更新master节点的kubectl,kubelet
$ yum -y install kubelet-1.17.4 kubectl-1.17.4 $ systemctl daemon-reload && systemctl restart kubelet
- 更新node节点
$ yum -y install kubeadm-1.17.4 $ kubeadm upgrade node --kubelet-version 1.17.4 $ yum -y install kubelet-1.17.4 $ systemctl daemon-reload && systemctl restart kubelet
- 验证升级结果
$ kubectl get nodes NAME STATUS ROLES AGE VERSION centos7-node1 Ready master 31h v1.17.4 centos7-node2 Ready master 30h v1.17.4 centos7-node3 NotReady master 30h v1.17.4 centos7-node7 Ready <none> 30h v1.17.4 centos7-node8 Ready <none> 29h v1.17.4
测试运行Nginx+Tomcat
参考用例： https://kubernetes.io/zh/docs/concepts/workloads/controllers/deployment/
- Nginx用例
$ docker pull nginx:1.14.2
$ docker tag nginx:1.14.2 harbor.magedu.com/baseimages/nginx:1.14.2
$ docker login harbor.magedu.com
$ docker push harbor.magedu.com/baseimages/nginx:1.14.2 #上传基础镜像到本地仓库
$ mkdir ~/kubeadm_demo/nginx && vim ~/kubeadm_demo/nginx/nginx.yml
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
labels:
app: nginx
spec:
replicas: 1
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: harbor.magedu.com/baseimages/nginx:1.14.2
ports:
- containerPort: 80
---
kind: Service
apiVersion: v1
metadata:
labels:
app: magedu-nginx-service-label
name: magedu-nginx-service
namespace: default
spec:
type: NodePort
ports:
- name: http
port: 80
protocol: TCP
targetPort: 80
nodePort: 30004
selector:
app: nginx
$ kubectl apply -f ~/kubeadm_demo/nginx/nginx.yml
$ kubectl get pod -A
$ kubectl get svc -A
$ kubectl logs nginx-deployment-79dbb87ff9-w5f87 -f #查看nginx-deployment 访问日志haproxy和keepalived配置
- 需要新增一个VIP（LB）
- 将LB映射到haproxy对应的nodeport上
- tomcat配置
$ docker pull tomcat $ docker run --name tomcat -d -p 8080:8080 tomcat $ docker exec -it tomcat bash :/usr/local/tomcat# cd webapps :/usr/local/tomcat/webapps# echo "tomcat.app" > app/index.html
测试访问 http://192.168.56.11:8080/app/
在harbor创建linux公开仓库
- 准备dockerfile
$ mkdir ~/kubeadm_demo/tomcat && vim ~/kubeadm_demo/tomcat/Dockerfile FROM tomcat ADD ./app /usr/local/tomcat/webapps/app/ $ cd ~/kubeadm_demo/tomcat && mkdir app && echo "tomcat APP" > app/index.html $ docker build -t harbor.magedu.com/linux/tomcat:app . #构建镜像 $ docker run --name t1 -it --rm -p 8080:8080 harbor.magedu.com/linux/tomcat:app #测试镜像是否有误 $ docker push harbor.magedu.com/linux/tomcat:app
- 业务pod创建
[ tomcat]# vim tomcat.yml
apiVersion: apps/v1
kind: Deployment
metadata:
name: tomcat-deployment
labels:
app: tomcat
spec:
replicas: 1
selector:
matchLabels:
app: tomcat
template:
metadata:
labels:
app: tomcat
spec:
containers:
- name: tomcat
image: harbor.magedu.com/linux/tomcat:app
ports:
- containerPort: 80
---
kind: Service
apiVersion: v1
metadata:
labels:
app: magedu-tomcat-service-label
name: magedu-tomcat-service
namespace: default
spec:
type: NodePort
ports:
- name: http
port: 80
protocol: TCP
targetPort: 8080
#nodePort: 30005
selector:
app: tomcat- nginx代理请求到tomcat
$ cd ~/kubeadm_demo/nginx && vim Dockerfile
FROM nginx:1.14.2
ADD default.conf /etc/nginx/conf.d/
$ vim default.conf
server {
listen 80;
server_name localhost;
location /app {
proxy_pass http://magedu-tomcat-service; #tomcat的svc
}
}
$ docker build -t harbor.magedu.com/baseimages/nginx:v0.1 .
$ docker push harbor.magedu.com/baseimages/nginx:v0.1
$ vim nginx.yml
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
labels:
app: nginx
spec:
replicas: 1
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: harbor.magedu.com/baseimages/nginx:v0.1 #修改镜像
ports:
- containerPort: 80
---
kind: Service
apiVersion: v1
metadata:
labels:
app: magedu-nginx-service-label
name: magedu-nginx-service
namespace: default
spec:
type: NodePort
ports:
- name: http
port: 80
protocol: TCP
targetPort: 80
nodePort: 30004
selector:
app: nginx
$ kubectl apply -f nginx.yml #此时访问 http://192.168.56.11:30004/app/index.html #即可token过期问题
kubeadm token generate kubeadm token create kubeadm token delete
相关推荐
kunyus 2020-10-28
hubanbei00的家园 2020-10-25
btqszl 2020-10-21
shurenyun 2020-08-19
CurrentJ 2020-08-18
ioniconline 2020-09-22
远远的山 2020-11-09
kaidiphp 2020-10-13
JustHaveTry 2020-09-29
cloudvtech 2020-09-18
BigDataMining 2020-08-21
朱培知浅ZLH 2020-11-16
cdbdqn00 2020-11-12
达观数据 2020-11-11
JustinChia 2020-11-11
jingtao 2020-11-08
大叔比较胖 2020-10-30
gracecxj 2020-10-30
onepiecedn 2020-10-29