Kubernetes 1.25 集群搭建
Posted
tags:
篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了Kubernetes 1.25 集群搭建相关的知识，希望对你有一定的参考价值。
文章目录
- 准备工作：
- 修改系统默认源 -- 阿里云 [可选步骤]
- 安装依赖软件
- 修改Hostname，配置hosts
- 关闭防火墙、关闭Selinux、关闭SWAP
- 内核升级
- 开启IPVS模块、内核优化
- 实验步骤：
- 1.1 nginx配置文件（主/备一样）
- 1.2 keepalived配置文件（Nginx Master）
- 1.3 keepalived配置文件（Nginx Backup）
- 1.4 keepalived配置文件（Nginx Backup）
- 1.5 启动并设置开机启动
- 扩展知识：
角色 | IP | 系统 |
k8s-master01、Keepalived(主)+nginx | 172.16.3.225/21 | Rocky Linux release 8.6 (Green Obsidian) |
k8s-master02、Keepalived(从)+Nginx | 172.16.3.226/21 | Rocky Linux release 8.6 (Green Obsidian) |
k8s-master03、Keepalived(从)+Nginx | 172.16.3.227/21 | Rocky Linux release 8.6 (Green Obsidian) |
k8s-node01 | 172.16.4.184/21 | Rocky Linux release 8.6 (Green Obsidian) |
VIP | 172.16.3.254/21 |
准备工作：
注意：这里的所有操作每个主机都得执行；；；
- 在此之前先确定所有主机的时间是一致的；；；
- 在此之前先确定所有主机的时间是一致的；；；
- 在此之前先确定所有主机的时间是一致的；；；
修改系统默认源 – 阿里云 [可选步骤]
sed -e s|^mirrorlist=|#mirrorlist=|g \\
-e s|^#baseurl=http://dl.rockylinux.org/$contentdir|baseurl=https://mirrors.aliyun.com/rockylinux|g \\
-i.bak \\
/etc/yum.repos.d/Rocky-*.repo
dnf makecache
安装依赖软件
dnf install ipvsadm ipset tar bash-completion yum-utils device-mapper-persistent-data lvm2 -y
修改Hostname，配置hosts
172.16.3.225设置主机名： hostnamectl set-hostname k8s-master01
172.16.3.226设置主机名： hostnamectl set-hostname k8s-master02
172.16.3.227设置主机名： hostnamectl set-hostname k8s-master03
172.16.4.184设置主机名： hostnamectl set-hostname k8s-node01
cat >> /etc/hosts << EOF
172.16.3.225 k8s-master01
172.16.3.226 k8s-master02
172.16.3.227 k8s-master03
172.16.4.184 k8s-node01
172.16.3.254 vip.apiserver
EOF
关闭防火墙、关闭Selinux、关闭SWAP
systemctl disable firewalld --now
sed -i s/SELINUX=enforcing/SELINUX=disabled/g /etc/selinux/config
swapoff -a && sed -i / swap / s/^\\(.*\\)$/#\\1/g /etc/fstab
内核升级
# 查看内核版本
uname -sr
# 0、升级所有软件包
dnf update -y && dnf upgrade -y
# 1、下载公钥
rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
dnf install https://www.elrepo.org/elrepo-release-8.el8.elrepo.noarch.rpm -y
# 2、仓库启用后，列出可用的内核相关包：
dnf --disablerepo="*" --enablerepo="elrepo-kernel" list available
kernel-lt： long term support：长期支持版
kernel-ml： mainline stable： 主线稳定版
# 3、选择自己的版本进行安装,安装最新版
dnf --enablerepo=elrepo-kernel install kernel-ml kernel-ml-devel kernel-ml-headers -y
# 4、重启
shutdown -r now
# 5、查看内核
uname -sr
开启IPVS模块、内核优化
cat > /etc/sysconfig/modules/ipvs.modules <<EOF
#!/bin/bash
ipvs_modules="ip_vs ip_vs_lc ip_vs_wlc ip_vs_rr ip_vs_wrr ip_vs_lblc ip_vs_lblcr ip_vs_dh ip_vs_sh ip_vs_fo ip_vs_nq ip_vs_sed ip_vs_ftp nf_conntrack br_netfilter"
for kernel_module in \\$ipvs_modules; do
/sbin/modinfo -F filename \\$kernel_module > /dev/null 2>&1
if [ $? -eq 0 ]; then
/sbin/modprobe \\$kernel_module
fi
done
EOF
# modprobe br_netfilter
chmod 755 /etc/sysconfig/modules/ipvs.modules && bash /etc/sysconfig/modules/ipvs.modules && lsmod | grep ip_vs
cat >> /etc/security/limits.conf << EOF
* soft nproc 65535
* hard nproc 130070
* soft nofile 65535
* hard nofile 130070
EOF
cat >> /etc/sysctl.conf << EOF
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
EOF
sysctl -p
实验步骤：
1、安装Keepalived+Nginx
- 在Master上安装
dnf install epel-release -y
dnf install nginx keepalived -y
1.1 nginx配置文件（主/备一样）
cp /etc/nginx/nginx.conf,.bak
cat > /etc/nginx/nginx.conf << EOF
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;
include /usr/share/nginx/modules/*.conf;
events
worker_connections 1024;
# 四层负载均衡，为三台Master apiserver组件提供负载均衡
stream
log_format main $remote_addr $upstream_addr - [$time_local] $status $upstream_bytes_sent;
access_log /var/log/nginx/k8s-access.log main;
error_log /var/log/nginx/k8s-error.log error;
upstream k8s-apiserver
server 172.16.3.225:6443; # Master1 APISERVER IP:PORT
server 172.16.3.226:6443; # Master2 APISERVER IP:PORT
server 172.16.3.227:6443; # Master3 APISERVER IP:PORT
server
listen 16443; # 由于nginx与master节点复用，这个监听端口不能是6443，否则会冲突
proxy_pass k8s-apiserver;
http
log_format main $remote_addr - $remote_user [$time_local] "$request"
$status $body_bytes_sent "$http_referer"
"$http_user_agent" "$http_x_forwarded_for";
access_log /var/log/nginx/access.log main;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
include /etc/nginx/mime.types;
default_type application/octet-stream;
EOF
1.2 keepalived配置文件（Nginx Master）
- 172.16.3.225 配置
cp /etc/keepalived/keepalived.conf,.bak
cat > /etc/keepalived/keepalived.conf << EOF
global_defs
notification_email
acassen@firewall.loc
failover@firewall.loc
sysadmin@firewall.loc
notification_email_from Alexandre.Cassen@firewall.loc
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id NGINX_MASTER
vrrp_script check_nginx
script "/etc/keepalived/check_nginx.sh"
vrrp_instance VI_1
state MASTER
interface ens192 # 修改为实际网卡名
virtual_router_id 51 # VRRP 路由 ID实例，每个实例是唯一的
priority 100 # 优先级，备服务器设置 低于100
advert_int 1 # 指定VRRP 心跳包通告间隔时间，默认1秒
authentication
auth_type PASS
auth_pass 1111
# 虚拟IP
virtual_ipaddress
172.16.3.254/21
track_script
check_nginx
EOF
- vrrp_script：指定检查nginx工作状态脚本（根据nginx状态判断是否故障转移）
- virtual_ipaddress：虚拟IP（VIP）
准备上述配置文件中检查nginx运行状态的脚本：
cat > /etc/keepalived/check_nginx.sh << EOF
#!/bin/bash
count=$(ss -antp |grep 16443 |egrep -cv "grep|$$")
if [ "$count" -eq 0 ];then
exit 1
else
exit 0
fi
EOF
chmod +x /etc/keepalived/check_nginx.sh
1.3 keepalived配置文件（Nginx Backup）
- 172.16.3.226 配置
cat > /etc/keepalived/keepalived.conf << EOF
global_defs
notification_email
acassen@firewall.loc
failover@firewall.loc
sysadmin@firewall.loc
notification_email_from Alexandre.Cassen@firewall.loc
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id NGINX_BACKUP
vrrp_script check_nginx
script "/etc/keepalived/check_nginx.sh"
vrrp_instance VI_1
state BACKUP
interface ens192
virtual_router_id 51 # VRRP 路由 ID实例，每个实例是唯一的
priority 90
advert_int 1
authentication
auth_type PASS
auth_pass 1111
virtual_ipaddress
172.16.3.254/21
track_script
check_nginx
EOF
准备上述配置文件中检查nginx运行状态的脚本：
cat > /etc/keepalived/check_nginx.sh << "EOF"
#!/bin/bash
count=$(ss -antp |grep 16443 |egrep -cv "grep|$$")
if [ "$count" -eq 0 ];then
exit 1
else
exit 0
fi
EOF
chmod +x /etc/keepalived/check_nginx.sh
注：keepalived根据脚本返回状态码（0为工作正常，非0不正常）判断是否故障转移。
1.4 keepalived配置文件（Nginx Backup）
- 172.16.3.227 配置
cat > /etc/keepalived/keepalived.conf << EOF
global_defs
notification_email
acassen@firewall.loc
failover@firewall.loc
sysadmin@firewall.loc
notification_email_from Alexandre.Cassen@firewall.loc
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id NGINX_BACKUP
vrrp_script check_nginx
script "/etc/keepalived/check_nginx.sh"
vrrp_instance VI_1
state BACKUP
interface ens192
virtual_router_id 51 # VRRP 路由 ID实例，每个实例是唯一的
priority 80
advert_int 1
authentication
auth_type PASS
auth_pass 1111
virtual_ipaddress
172.16.3.254/21
track_script
check_nginx
EOF
准备上述配置文件中检查nginx运行状态的脚本：
cat > /etc/keepalived/check_nginx.sh << "EOF"
#!/bin/bash
count=$(ss -antp |grep 16443 |egrep -cv "grep|$$")
if [ "$count" -eq 0 ];then
exit 1
else
exit 0
fi
EOF
chmod +x /etc/keepalived/check_nginx.sh
注：keepalived根据脚本返回状态码（0为工作正常，非0不正常）判断是否故障转移
1.5 启动并设置开机启动
systemctl daemon-reload
systemctl enable nginx --now
systemctl enable keepalived --now
systemctl status nginx
systemctl status keepalived
2、安装Containerd
- 所有主机安装、这里我用的是清华源
yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo sed -i s+download.docker.com+mirrors.tuna.tsinghua.edu.cn/docker-ce+ /etc/yum.repos.d/docker-ce.repo
dnf install containerd.io -y
2.1 配置Containerd
containerd config default > /etc/containerd/config.toml # 导出Containerd默认配置文件
sed -i "s#/var/lib/containerd#/data/containerd#" /etc/containerd/config.toml
sed -i "s#/run/containerd#/data/containerd/state#" /etc/containerd/config.toml
sed -i "s#/data/containerd/state/containerd.sock#/run/containerd/containerd.sock#" /etc/containerd/config.toml
sed -i "s#/opt/containerd#/data/containerd/containers#" /etc/containerd/config.toml
sed -i s#k8s.gcr.io#registry.cn-hangzhou.aliyuncs.com/google_containers# /etc/containerd/config.toml
sed -i s#SystemdCgroup = false#SystemdCgroup = true# /etc/containerd/config.toml
cat > /etc/crictl.yaml << EOF
runtime-endpoint: unix:///run/containerd/containerd.sock
image-endpoint: unix:///run/containerd/containerd.sock
timeout: 10 # 超时时间
debug: false # debug是否输出debug信息
EOF
mkdir /data
systemctl enable containerd --now
systemctl status containerd
3、安装Kubernetes
- 所有主机执行、这里我用的是清华源
cat > /etc/yum.repos.d/kubernetes.repo << EOF
[kubernetes]
name=kubernetes
baseurl=https://mirrors.tuna.tsinghua.edu.cn/kubernetes/yum/repos/kubernetes-el7-$basearch
enabled=1
EOF
dnf install -y --nogpgcheck kubelet kubeadm kubectl
systemctl enable kubelet --now
3.1 Kubernetes集群初始化准备
- 172.16.3.225上执行
kubeadm config print init-defaults > kubeadm-init.yaml
cat > kubeadm-init.yaml << EOF
apiVersion: kubeadm.k8s.io/v1beta3
bootstrapTokens:
- groups:
- system:bootstrappers:kubeadm:default-node-token
token: abcdef.0123456789abcdef
ttl: 24h0m0s
usages:
- signing
- authentication
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 172.16.3.225 # 修改成本机IP
bindPort: 6443
nodeRegistration:
criSocket: unix:///var/run/containerd/containerd.sock
imagePullPolicy: IfNotPresent
name: k8s-master01 # 修改成本机名字
taints: null
---
apiServer:
timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta3
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controlPlaneEndpoint: 172.16.3.254:16443 # 新增写自己的VIP
controllerManager:
dns:
etcd:
local:
dataDir: /var/lib/etcd
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers # 指定阿里云镜像
kind: ClusterConfiguration
kubernetesVersion: 1.25.2 # 修改成自己Kubernetes版本
networking:
dnsDomain: cluster.local
podSubnet: 10.244.0.0/16 # 新增Pod地址
serviceSubnet: 10.96.0.0/12
scheduler:
# 新增如下内容： 开启Kube-Proxy IPVS模块
---
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
mode: ipvs
EOF
kubeadm config images pull --config=kubeadm-init.yaml # 下载镜像
kubeadm init --config kubeadm-init.yaml | tee kubeadm-init.log # 初始化集群
- 以下内容是初始化输出的流程：
[root@k8s-master1 ~]# kubeadm init --config kubeadm-init.yaml | tee kubeadm-init.log
[init] Using Kubernetes version: v1.25.2
[preflight] Running pre-flight checks
[WARNING FileExisting-tc]: tc not found in system path
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using kubeadm config images pull
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.16.3.225 172.16.3.254]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master01 localhost] and IPs [172.16.3.225 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master01 localhost] and IPs [172.16.3.225 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
W0929 15:46:26.363353 15180 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "admin.conf" kubeconfig file
W0929 15:46:26.523144 15180 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "kubelet.conf" kubeconfig file
W0929 15:46:26.745022 15180 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
W0929 15:46:27.021676 15180 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 11.528231 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node k8s-master01 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[mark-control-plane] Marking the node k8s-master01 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: abcdef.0123456789abcdef
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
W0929 15:46:42.544999 15180 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy
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/
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 172.16.3.254:16443 --token abcdef.0123456789abcdef \\
--discovery-token-ca-cert-hash sha256:872c34cc291025d258f6dc10de3f1789086f2d82a2a2156806b16ded736e62de \\
--control-plane
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 172.16.3.254:16443 --token abcdef.0123456789abcdef \\
--discovery-token-ca-cert-hash sha256:419e25aa5089819dc6cdae3996b92e950e28504ecdd33bdca230ec5379731764
在Master上执行：
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
以下节点加入角色Master执行：
kubeadm join 172.16.3.254:16443 --token abcdef.0123456789abcdef \\
--discovery-token-ca-cert-hash sha256:872c34cc291025d258f6dc10de3f1789086f2d82a2a2156806b16ded736e62de \\
--control-plane
以下节点加入角色Node执行：
kubeadm join 172.16.3.254:16443 --token abcdef.0123456789abcdef \\
--discovery-token-ca-cert-hash sha256:419e25aa5089819dc6cdae3996b92e950e28504ecdd33bdca230ec5379731764
3.2、如果在加入集群出错执行以下步骤
报错内容：
[failure loading certificate for CA: couldnt load the certificate file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory, failure loading key for service account: couldnt load the private key file /etc/kubernetes/pki/sa.key: open /etc/kubernetes/pki/sa.key: no such file or directory, failure loading certificate for front-proxy CA: couldnt load the certificate file /etc/kubernetes/pki/front-proxy-ca.crt: open /etc/kubernetes/pki/front-proxy-ca.crt: no such file or directory, failure loading certificate for etcd CA: couldnt load the certificate file /etc/kubernetes/pki/etcd/ca.crt: open /etc/kubernetes/pki/etcd/ca.crt: no such file or directory]
cd /etc/kubernetes && tar -zcf k8s-key.tar.gz admin.conf pki/ca.* pki/sa.* pki/front-proxy-ca.* pki/etcd/ca.*
scp /etc/kubernetes/k8s-key.tar.gz k8s-master02:/etc/kubernetes
scp /etc/kubernetes/k8s-key.tar.gz k8s-master03:/etc/kubernetes
另外两台Master压缩证书，再次加入进去测试；
4、安装Calico网络
- 在Master01上执行
kubectl get no # 查看Node状态都是NotReady是因为网络查件没有准备就绪
NAME STATUS ROLES AGE VERSION
k8s-master01 NotReady control-plane 5m54s v1.25.2
k8s-master02 NotReady control-plane 4m13s v1.25.2
k8s-master03 NotReady control-plane 4m14s v1.25.2
k8s-node01 NotReady <none> 2m40s v1.25.2
wget https://projectcalico.docs.tigera.io/manifests/calico.yaml
修改CALICO_IPV4POOL_CIDR，改成自己设置的pod地址范围，注意缩进
4551 - name: CALICO_IPV4POOL_CIDR
4552 value: "10.244.0.0/16"
kubectl apply -f calico.yaml
kubectl get po -A # 耐心等待所有容器变成Running状态
kubectl get no
NAME STATUS ROLES AGE VERSION
k8s-master01 Ready control-plane 13m v1.25.2
k8s-master02 Ready control-plane 12m v1.25.2
k8s-master03 Ready control-plane 12m v1.25.2
k8s-node01 Ready <none> 10m v1.25.2
5、安装Kubernetes Tables功能
cat >> ~/.bashrc << EOF
source /usr/share/bash-completion/bash_completion
source <(kubectl completion bash)
EOF
source ~/.bashrc
扩展知识：
1、部署Ingress
wget https://ghproxy.com/https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/baremetal/deploy.yaml
grep "image:" deploy.yaml # 将Yaml文件的镜像修改地址成国内的
image: lank8s.cn/ingress-nginx/controller:v1.3.1
image: lank8s.cn/ingress-nginx/kube-webhook-certgen:v1.3.0
image: lank8s.cn/ingress-nginx/kube-webhook-certgen:v1.3.0
kubectl get po,svc -n ingress-nginx
NAME READY STATUS RESTARTS AGE
pod/ingress-nginx-admission-create-z844l 0/1 Completed 0 73s
pod/ingress-nginx-admission-patch-2x2sq 0/1 Completed 0 73s
pod/ingress-nginx-controller-554f784744-g7zp6 1/1 Running 0 73s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/ingress-nginx-controller NodePort 10.104.115.74 <none> 80:31743/TCP,443:32008/TCP 73s
service/ingress-nginx-controller-admission ClusterIP 10.97.58.184 <none>
2、部署个Pod 测试一下网络以及Ingress是否正常
cat > nginx.yaml << EOF
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx
namespace: default
spec:
selector:
matchLabels:
app: nginx
replicas: 1
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:latest
ports:
- containerPort: 80
name: nginx
volumeMounts:
- name: localtime
mountPath: /etc/localtime
volumes:
- name: localtime
hostPath:
path: /usr/share/zoneinfo/Asia/Shanghai
restartPolicy: Always
---
apiVersion: v1
kind: Service
metadata:
name: nginx
namespace: default
spec:
selector:
app: nginx
type: ClusterIP
ports:
- name: nginx
protocol: TCP
port: 80
targetPort: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx
namespace: default
spec:
ingressClassName: nginx
rules:
- host: foo.bar.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: nginx
port:
number: 80
- 测试一下Nginx Pod是否正常
kubectl get po,svc,ingress
NAME READY STATUS RESTARTS AGE
pod/nginx-8456669dfb-678d9 1/1 Running 0 67s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 28m
service/nginx ClusterIP 10.106.188.230 <none> 80/TCP 67s
NAME CLASS HOSTS ADDRESS PORTS AGE
ingress.networking.k8s.io/nginx nginx foo.bar.com 80 67s
curl -l http://foo.bar.com:31743/
以上是关于Kubernetes 1.25 集群搭建的主要内容，如果未能解决你的问题，请参考以下文章
40项增强功能更新，2个功能被弃用，Kubernetes 1.25发布！
40项增强功能更新，2个功能被弃用，Kubernetes 1.25发布