ConfigMap 挂载
---
# Source: grafana/templates/tests/test-configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: grafana-test
namespace: network-zabbix
annotations:
"helm.sh/hook": test
"helm.sh/hook-delete-policy": "before-hook-creation,hook-succeeded"
labels:
helm.sh/chart: grafana-8.10.0
app.kubernetes.io/name: grafana
app.kubernetes.io/instance: grafana
app.kubernetes.io/version: "11.5.1"
data:
run.sh: |-
@test "Test Health" {
url="http://grafana/api/health"
code=$(wget --server-response --spider --timeout 90 --tries 10 ${url} 2>&1 | awk '/^ HTTP/{print $2}')
[ "$code" == "200" ]
}
---
# Source: grafana/templates/tests/test.yaml
apiVersion: v1
kind: Pod
metadata:
name: grafana-test
labels:
helm.sh/chart: grafana-8.10.0
app.kubernetes.io/name: grafana
app.kubernetes.io/instance: grafana
app.kubernetes.io/version: "11.5.1"
annotations:
"helm.sh/hook": test
"helm.sh/hook-delete-policy": "before-hook-creation,hook-succeeded"
namespace: network-zabbix
spec:
serviceAccountName: grafana-test
containers:
- name: grafana-test
image: "harbor.sensoro.com/bats/bats:v1.4.1"
imagePullPolicy: "IfNotPresent"
command: ["/opt/bats/bin/bats", "-t", "/tests/run.sh"]
volumeMounts:
- mountPath: /tests
name: tests
readOnly: true
volumes:
- name: tests
configMap:
name: grafana-test
restartPolicy: Never
PVC挂载到 deployment
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: my-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-deployment
spec:
replicas: 1
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: my-container
image: nginx:1.14.2
ports:
- containerPort: 80
volumeMounts:
- name: my-volume
mountPath: /usr/share/nginx/html
volumes:
- name: my-volume
persistentVolumeClaim:
claimName: my-pvc
apiVersion: apps/v1:指定使用的 Kubernetes API 版本,适用于 Deployment 资源。kind: Deployment:表明这是一个 Deployment 对象。metadata.name: my-deployment:给 Deployment 命名为my-deployment。replicas: 1:指定要创建的 Pod 副本数量为 1。selector和template.metadata.labels:用于匹配 Deployment 管理的 Pod。containers:定义容器的相关信息。name: my-container:容器的名称。image: nginx:1.14.2:使用的容器镜像。ports:容器暴露的端口。volumeMounts:定义容器内的挂载点,name对应volumes中的名称,mountPath是容器内的挂载路径。
volumes:定义 Pod 内的卷,persistentVolumeClaim.claimName指定要使用的 PVC 名称。
Deployment 多副本默认挂载同一个 PV,若要独立存储则需额外配置
Statefulset挂载PVC的基本型
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: my-statefulset
spec:
serviceName: "my-statefulset-service"
replicas: 3
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: my-container
image: nginx:1.14.2
ports:
- containerPort: 80
name: web
volumeMounts:
- name: my-persistent-storage
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: my-persistent-storage
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 1Gi
StatefulSet 会为每个 Pod 实例自动创建独立的 PVC 并绑定到不同的 PV,以满足有状态应用的需求
readinessProbe健康检查
在 Kubernetes 中,readinessProbe 常用的配置方式主要有以下三种实现形式:
- HTTP GET 请求检查
- 通过向容器 IP 发送 HTTP 请求验证服务可用性
- 典型配置字段示例:
readinessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 5 # 容器启动后等待 5 秒开始检查 periodSeconds: 10 # 每 10 秒执行一次检查 timeoutSeconds: 1 # 超时时间 1 秒 successThreshold: 1 # 成功 1 次即标记就绪 failureThreshold: 3 # 连续失败 3 次标记未就绪
- Exec 命令执行检查
- 在容器内执行指定命令,根据退出码判断状态(0 为成功)
- 典型配置示例:
readinessProbe: exec: command: - sh - -c - "ps aux | grep 'app_main_process'" failureThreshold: 2 periodSeconds: 5
- TCP Socket 端口检查
- 直接检查指定端口是否开放
- 典型配置示例:
readinessProbe: tcpSocket: port: 3306 initialDelaySeconds: 15 periodSeconds: 20
关键参数说明:
initialDelaySeconds:容器启动后延迟探测的时间(避免启动过程误判)periodSeconds:探测频率,建议大于服务响应时间timeoutSeconds:单次探测超时阈值successThreshold:成功次数阈值(默认 1)failureThreshold:失败次数阈值(默认 3)
配置建议:
- 对延迟敏感的服务应适当增大
initialDelaySeconds - 生产环境建议
failureThreshold≥2,避免网络抖动导致误剔除 - HTTP 检查推荐配合应用层健康检查接口使用
- 高并发场景建议探测间隔(
periodSeconds) ≥10 秒,避免检查请求成为额外负载
转载请注明来源,欢迎对文章中的引用来源进行考证,欢迎指出任何有错误或不够清晰的表达。可以在下面评论区评论,也可以邮件至 365433079@qq.com