样式表一般用于大型网站wordpress 目录排序

样式表一般用于大型网站,wordpress 目录排序,在线设计网站免费,织梦网站栏目修改教程k8s部署 metrics-server 是 Kubernetes 实现资源监控#xff08;如 kubectl top、HPA 自动扩缩容#xff09;的核心组件#xff0c;在部署过程中遇到过以下问题 镜像拉取失败#xff08;k8s.gcr.io 镜像国内无法访问#xff09;#xff1b;证书验证问题#xff08;需跳…k8s部署metrics-server是 Kubernetes 实现资源监控如kubectl top、HPA 自动扩缩容的核心组件在部署过程中遇到过以下问题镜像拉取失败k8s.gcr.io镜像国内无法访问证书验证问题需跳过 TLS 验证或配置正确证书API Server 连接问题需指定kubelet-insecure-tls。部署步骤如下1.步骤 1下载官方部署文件并修改# 下载官方 yaml也可手动创建 wget https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml -O metrics-server.yaml2.步骤 2修改metrics-server.yaml关键配置打开metrics-server.yaml做以下 3 处核心修改# 原镜像国内无法访问 # image: k8s.gcr.io/metrics-server/metrics-server:v0.7.0 # 替换为阿里云镜像适配 v0.7.0 版本 image: registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-server:v0.7.03. 添加启动参数解决证书 / 连接问题在Deployment的args部分新增以下参数关键spec: template: spec: containers: - name: metrics-server args: - --cert-dir/tmp - --secure-port4443 # 新增以下 3 个参数 - --kubelet-insecure-tls # 跳过 kubelet TLS 验证测试环境推荐生产建议配置证书 - --kubelet-preferred-address-typesInternalIP,ExternalIP,Hostname # 指定 kubelet 地址类型 - --metric-resolution15s # 监控数据采集间隔4.可选调整资源限制根据集群规模resources: requests: cpu: 100m memory: 100Mi limits: cpu: 500m memory: 512Mi5.部署metrics-serverkubectl apply -f metrics-server.yaml6.验证部署kubectl get pods -n kube-system -l k8s-appmetrics-server # 正常输出STATUS 为 Running # NAME READY STATUS RESTARTS AGE # metrics-server-7f987d68c4-9x8zl 1/1 Running 0 5m检查 Pod 日志排查启动失败kubectl logs -n kube-system $(kubectl get pods -n kube-system -l k8s-appmetrics-server -o name) # 常见日志错误及解决 # - x509: certificate signed by unknown authority → 确认已加 --kubelet-insecure-tls # - unable to reach kubelet → 检查 --kubelet-preferred-address-types 参数 # - image pull failed → 确认镜像地址正确验证 API 可用性核心metrics-server会注册metrics.k8s.ioAPI检查是否正常# 查看节点资源使用 kubectl top nodes # 输出示例 # NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% # k8s-master 123m 6% 1200Mi 30% # k8s-node1 89m 4% 980Mi 25% # 查看 Pod 资源使用 kubectl top pods -n kube-system # 输出包含 metrics-server 自身的资源占用二.本次部署环境使用修改后的yaml文件如下可直接使用apiVersion: v1 kind: ServiceAccount metadata: labels: k8s-app: metrics-server name: metrics-server namespace: kube-system --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: labels: k8s-app: metrics-server rbac.authorization.k8s.io/aggregate-to-admin: true rbac.authorization.k8s.io/aggregate-to-edit: true rbac.authorization.k8s.io/aggregate-to-view: true name: system:aggregated-metrics-reader rules: - apiGroups: - metrics.k8s.io resources: - pods - nodes verbs: - get - list - watch --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: labels: k8s-app: metrics-server name: system:metrics-server rules: - apiGroups: - resources: - pods - nodes - nodes/stats - namespaces - configmaps verbs: - get - list - watch --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: labels: k8s-app: metrics-server name: metrics-server-auth-reader namespace: kube-system roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: extension-apiserver-authentication-reader subjects: - kind: ServiceAccount name: metrics-server namespace: kube-system --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: labels: k8s-app: metrics-server name: metrics-server:system:auth-delegator roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: system:auth-delegator subjects: - kind: ServiceAccount name: metrics-server namespace: kube-system --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: labels: k8s-app: metrics-server name: system:metrics-server roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: system:metrics-server subjects: - kind: ServiceAccount name: metrics-server namespace: kube-system --- apiVersion: v1 kind: Service metadata: labels: k8s-app: metrics-server name: metrics-server namespace: kube-system spec: ports: - name: https port: 443 protocol: TCP targetPort: 8443 selector: k8s-app: metrics-server --- apiVersion: apps/v1 kind: Deployment metadata: labels: k8s-app: metrics-server name: metrics-server namespace: kube-system spec: selector: matchLabels: k8s-app: metrics-server strategy: rollingUpdate: maxUnavailable: 0 template: metadata: labels: k8s-app: metrics-server spec: containers: - args: - --cert-dir/tmp - --secure-port8443 - --kubelet-preferred-address-typesInternalIP,ExternalIP,Hostname - --kubelet-use-node-status-port - --metric-resolution15s - --kubelet-insecure-tls - --authorization-always-allow-paths/livez,/readyz image: swr.cn-east-2.myhuaweicloud.com/kuboard-dependency/metrics-server:v0.5.0 imagePullPolicy: IfNotPresent livenessProbe: failureThreshold: 3 httpGet: path: /livez port: https scheme: HTTPS periodSeconds: 10 name: metrics-server ports: - containerPort: 8443 name: https protocol: TCP readinessProbe: failureThreshold: 3 httpGet: path: /readyz port: https scheme: HTTPS initialDelaySeconds: 20 periodSeconds: 10 resources: requests: cpu: 100m memory: 200Mi securityContext: readOnlyRootFilesystem: true runAsNonRoot: true runAsUser: 1000 volumeMounts: - mountPath: /tmp name: tmp-dir nodeSelector: kubernetes.io/os: linux priorityClassName: system-cluster-critical serviceAccountName: metrics-server volumes: - emptyDir: {} name: tmp-dir --- apiVersion: apiregistration.k8s.io/v1 kind: APIService metadata: labels: k8s-app: metrics-server name: v1beta1.metrics.k8s.io spec: group: metrics.k8s.io groupPriorityMinimum: 100 insecureSkipTLSVerify: true service: name: metrics-server namespace: kube-system version: v1beta1 versionPriority: 100