做网站上传照片的尺寸wordpress首页自定义小工具

做网站上传照片的尺寸,wordpress首页自定义小工具,做网站交接需要哪些权限,南昌网站推广官方公告#xff1a;Ingress NGINX 将在 2026 年3月停止维护#xff0c;之后不会再有新 bug 修复或安全补丁。 这次官方宣布停止维护Ingress NGINX主要原因还是因为项目长期依赖少数维护者、并且今年暴露过严重安全事件#xff0c;还有一个原因是大量 NGINX 自定义配置、各…官方公告Ingress NGINX 将在2026 年3月停止维护之后不会再有新 bug 修复或安全补丁。这次官方宣布停止维护Ingress NGINX主要原因还是因为项目长期依赖少数维护者、并且今年暴露过严重安全事件还有一个原因是大量 NGINX 自定义配置、各种注解annotations、自定义模板使得开发者几乎“被锁定”在老旧架构中。“停止维护”并不等于服务立即停止或失效目前系统继续运行不会因为公告立即宕掉。但风险增加未来若有新漏洞或安全事件使用者将无法获得官方补丁自行承担风险。所以短期内还可以继续使用后期就需要考虑替代品了大部分公司如果用了K8S把服务暴露给外网大概率都使用了Ingress NGINX。所以它宣布即将停止维护大家还是捏了一把汗还好在2026年3月才停止维护这就给企业留了缓冲时间。Kubernetes 的新方向是 Gateway API行业趋势已经不再是 “Ingress NGINX”而是标准化的Gateway API。Kubernetes 1.34 中 Gateway API 已进入GA通用可用阶段v1.0.0替代传统 Ingress 成为更灵活的流量管理方案。以下主流流量组件都支持 Gateway API。Istiohttps://istio.io/latest/Traefikhttps://doc.traefik.io/traefik/Konghttps://developer.konghq.com/HAProxyhttps://www.haproxy.com/blog本次实现在新搭建的kubernetes1.34集群尝试安装Traefik经过官网对比Traefik 3.x 是适配 Gateway API v1 的最佳选择。1.部署 Gateway API CRDsK8s 1.34 必备# 部署 Gateway API v1.0.0 CRDs官方源 kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml # 验证 CRDs 部署成功 kubectl get crds | grep gateway.networking.k8s.io # 输出包含 gatewayclasses.gateway.networking.k8s.io、gateways.gateway.networking.k8s.io、httproutes.gateway.networking.k8s.io 等即正常2.创建 Traefik 命名空间kubectl create namespace traefik3. 部署 Traefik RBAC 权限适配 Gateway APITraefik 需要访问 Gateway API 资源GatewayClass/Gateway/HTTPRoute 等创建traefik-rbac.yaml--- # ServiceAccount apiVersion: v1 kind: ServiceAccount metadata: name: traefik namespace: traefik --- # ClusterRole包含 Gateway API 资源权限 基础 K8s 资源权限 apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: traefik rules: # 基础网络资源 - apiGroups: [] resources: [services, endpoints, secrets] verbs: [get, list, watch] # Gateway API v1 资源核心 - apiGroups: [gateway.networking.k8s.io] resources: - gatewayclasses - gateways - httproutes - tcproutes - tlsroutes - referencegrants verbs: [get, list, watch, create, update, patch, delete] # 节点信息用于 DaemonSet 模式 - apiGroups: [] resources: [nodes] verbs: [get, list, watch] # Pod 信息用于端点发现 - apiGroups: [] resources: [pods] verbs: [get, list, watch] --- # ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: traefik roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: traefik subjects: - kind: ServiceAccount name: traefik namespace: traefik4.部署 Traefik 3.1DaemonSet 模式生产推荐--- # ConfigMapTraefik 基础配置 apiVersion: v1 kind: ConfigMap metadata: name: traefik-config namespace: traefik data: traefik.yaml: | api: insecure: true # 测试阶段开启仪表盘生产关闭 dashboard: true entryPoints: web: address: :80 # HTTP 入口 websecure: address: :443 # HTTPS 入口 traefik: address: :8080 # 仪表盘入口 providers: kubernetesGateway: # 启用 Gateway API 提供者核心 enabled: true namespace: * # 监听所有命名空间的 Gateway 资源 kubernetesIngress: # 可选保留 Ingress 兼容如需双模式 enabled: false log: level: INFO # 生产可改为 WARN accessLog: filePath: /dev/stdout # 访问日志输出到标准输出便于日志收集 --- # DaemonSet每个节点部署 Traefik使用 HostPort 暴露端口 apiVersion: apps/v1 kind: DaemonSet metadata: name: traefik namespace: traefik labels: app: traefik spec: selector: matchLabels: app: traefik template: metadata: labels: app: traefik spec: serviceAccountName: traefik hostNetwork: true # 使用主机网络确保 HostPort 生效 terminationGracePeriodSeconds: 60 containers: - name: traefik image: traefik:v3.1.0 # 适配 K8s 1.34 Gateway API v1镜像下载可参考官网 args: - --configfile/etc/traefik/traefik.yaml ports: - name: web containerPort: 80 hostPort: 80 # 主机 HTTP 端口 - name: websecure containerPort: 443 hostPort: 443 # 主机 HTTPS 端口 - name: traefik containerPort: 8080 hostPort: 8080 # 仪表盘端口 volumeMounts: - name: config mountPath: /etc/traefik securityContext: capabilities: drop: [ALL] add: [NET_BIND_SERVICE] # 允许绑定 80/443 端口 resources: limits: cpu: 1000m memory: 512Mi requests: cpu: 100m memory: 64Mi # 健康检查生产必备 livenessProbe: httpGet: path: /ping port: 8080 initialDelaySeconds: 10 periodSeconds: 10 readinessProbe: httpGet: path: /ping port: 8080 initialDelaySeconds: 5 periodSeconds: 5 volumes: - name: config configMap: name: traefik-config # 允许运行在控制平面节点按需开启 tolerations: - key: node-role.kubernetes.io/control-plane operator: Exists effect: NoSchedule - key: node-role.kubernetes.io/master operator: Exists effect: NoSchedule --- # Service暴露仪表盘测试用生产建议删除 apiVersion: v1 kind: Service metadata: name: traefik-dashboard namespace: traefik spec: selector: app: traefik ports: - name: traefik port: 8080 targetPort: 8080 nodePort: 30800 type: NodePort5.执行部署kubectl apply -f traefik-rbac.yaml kubectl apply -f traefik-daemonset.yaml6.验证 Traefik 部署# 检查 Traefik Pod 状态每个节点一个 PodRunning 状态 kubectl get pods -n traefik # 检查 Traefik 日志确认 Gateway API 提供者加载成功 kubectl logs -f traefik-pod-name -n traefik # 日志中包含 Provider kubernetesGateway started 即表示 Gateway API 适配成功 # 访问仪表盘验证测试用 curl http://节点IP:30800/dashboard/ # 能看到 Traefik 仪表盘界面即正常7.配置 Gateway API 资源核心验证Gateway API 核心资源关系GatewayClass网关类→Gateway网关实例→HTTPRoute路由规则。以下创建完整示例实现 Nginx 服务的流量转发。创建 GatewayClass绑定 Traefik 控制器GatewayClass是集群级资源定义网关的「类型」绑定 Traefik 控制器# traefik-gatewayclass.yaml apiVersion: gateway.networking.k8s.io/v1 kind: GatewayClass metadata: name: traefik-gateway-class spec: controllerName: traefik.io/gateway-controller # Traefik 3.x 固定标识 description: Traefik GatewayClass for K8s 1.34kubectl apply -f traefik-gatewayclass.yaml# 验证 GatewayClasskubectl get gatewayclass# 输出 traefik-gateway-classSTATUS 为 Accepted 即正常创建 Gateway网关实例暴露 80/443 端口Gateway是命名空间级资源对应 Traefik 的入口端口绑定上述 GatewayClass# traefik-gateway.yaml apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: traefik-gateway namespace: default # 可自定义命名空间 spec: gatewayClassName: traefik-gateway-class # 关联上述 GatewayClass listeners: # 监听端口配置对应 Traefik 的 entryPoints - name: web protocol: HTTP port: 80 allowedRoutes: namespaces: from: All # 允许所有命名空间的 HTTPRoute 关联 - name: websecure protocol: HTTPS port: 443 allowedRoutes: namespaces: from: All # 可选配置默认 TLS 证书需提前创建 Secret # tls: # certificateRefs: # - name: https-tls-secret # kind: Secretkubectl apply -f traefik-gateway.yaml # 验证 Gatewaykubectl get gateway # 输出 traefik-gatewaySTATUS 为 Ready 即正常需等待 Traefik 识别创建测试服务 HTTPRoute路由规则先部署 Nginx 测试服务再创建HTTPRoute关联 Gateway实现流量转发# nginx-test.yaml apiVersion: apps/v1 kind: Deployment metadata: name: nginx-test namespace: default spec: replicas: 1 selector: matchLabels: app: nginx-test template: metadata: labels: app: nginx-test spec: containers: - name: nginx image: nginx:1.22 ports: - containerPort: 80 --- apiVersion: v1 kind: Service metadata: name: nginx-test namespace: default spec: selector: app: nginx-test ports: - port: 80 targetPort: 80 type: ClusterIP --- # HTTPRoute路由规则关联 Gateway 和测试服务 apiVersion: gateway.networking.k8s.io/v1 kind: HTTPRoute metadata: name: nginx-httproute namespace: default spec: parentRefs: # 关联上述 Gateway - name: traefik-gateway namespace: default sectionName: web # 关联 Gateway 的 web 监听器80 端口 hostnames: # 自定义域名需配置 hosts 解析到节点 IP - nginx.test.com rules: # 路由规则 - matches: - path: type: PathPrefix value: / backendRefs: # 转发到测试服务 - name: nginx-test port: 80kubectl apply -f nginx-test.yaml# 验证 HTTPRoutekubectl get httproutes# 输出 nginx-httprouteSTATUS 为 Accepted 即正常验证 Gateway API 转发# 1. 配置本地 hosts示例 echo 节点IP nginx.test.com /etc/hosts # 2. 访问测试通过 Traefik 网关 80 端口 curl http://nginx.test.com # 输出 Nginx 默认页面 → 路由转发成功 # 3. 验证 Traefik 路由识别 kubectl logs -f traefik-pod-name -n traefik # 日志中包含 Added HTTPRoute default/nginx-httproute 即表示路由加载成功关键点回顾K8s 1.34 需手动部署 Gateway API v1.0.0 CRDsGA 版本无需特性门控Traefik 3.x 是适配 Gateway API v1 的核心版本需配置kubernetesGateway提供者Gateway API 核心资源流程GatewayClass集群级→Gateway命名空间级暴露端口→HTTPRoute路由规则关联服务生产环境需关闭 Traefik 仪表盘、启用 TLS 加密、配置资源限制和监控确保稳定性。