# 存储类型
– 本地存储：使用节点本地磁盘，性能好，但不支持数据持久化
– NFS：网络文件系统，支持多节点访问，适合共享存储
– iSCSI：块存储协议，性能较好，适合数据库等应用
– Ceph：分布式存储系统，支持块存储、文件存储和对象存储
– GlusterFS：分布式文件系统，适合大规模存储
– 云存储：AWS EBS、Azure Disk、GCP Persistent Disk等
– 存储插件：通过CSI（Container Storage Interface）集成第三方存储

# 存储类型选择因素
– 性能：I/O吞吐量和延迟
– 可靠性：数据冗余和故障恢复
– 可扩展性：支持的存储容量和并发访问
– 成本：存储成本和维护成本
– 集成性：与Kubernetes的集成程度

# 存储架构
– 本地存储：适合无状态应用和缓存
– 共享存储：适合有状态应用，如数据库
– 分布式存储：适合大规模应用和高可用场景
– 分层存储：根据数据访问频率使用不同存储类型

# 存储容量规划
– 预估应用存储需求：根据应用类型和数据量
– 预留增长空间：考虑数据增长和备份需求
– 多存储池：根据性能需求划分不同存储池
– 容量监控：实时监控存储使用情况

# 存储高可用
– 数据冗余：使用RAID、副本等技术
– 多路径：使用多路径技术提高可靠性
– 故障转移：配置存储故障自动转移
– 备份策略：定期备份数据，确保可恢复性

# 存储方案选择
– 小规模集群（< 100节点）：NFS、本地存储 - 中规模集群（100-500节点）：Ceph、GlusterFS - 大规模集群（> 500节点）：Ceph、云存储

# 应用场景
– 无状态应用：本地存储、NFS
– 有状态应用：Ceph、iSCSI、云存储
– 数据库：Ceph RBD、iSCSI、云存储
– 大数据：Ceph、GlusterFS
– 媒体存储：对象存储

# 性能需求
– 高IOPS：SSD存储、NVMe
– 高吞吐量：分布式存储、并行文件系统
– 低延迟：本地存储、NVMe

# 性能考虑因素
– I/O模式：随机I/O还是顺序I/O
– I/O大小：小I/O还是大I/O
– 并发访问：并发请求数
– 数据一致性：是否需要强一致性
– 延迟要求：应用对延迟的敏感程度

# 性能优化策略
– 使用SSD存储：提高I/O性能
– 配置适当的块大小：根据I/O模式调整
– 优化文件系统：选择适合的文件系统和挂载选项
– 使用缓存：使用缓存减少I/O操作
– 负载均衡：分散存储负载

# 创建静态PV
$ kubectl apply -f – << EOF apiVersion: v1 kind: PersistentVolume metadata: name: pv-nfs labels: type: nfs spec: capacity: storage: 10Gi accessModes: - ReadWriteMany nfs: server: 192.168.1.100 path: /exports persistentVolumeReclaimPolicy: Retain EOF # 查看PV状态 $ kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pv-nfs 10Gi RWX Retain Available 5m # 创建PVC $ kubectl apply -f - << EOF apiVersion: v1 kind: PersistentVolumeClaim metadata: name: pvc-nfs namespace: default spec: accessModes: - ReadWriteMany resources: requests: storage: 5Gi selector: matchLabels: type: nfs EOF # 查看PVC状态 $ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE pvc-nfs Bound pv-nfs 10Gi RWX 5m # 创建使用PVC的Pod $ kubectl apply -f - << EOF apiVersion: v1 kind: Pod metadata: name: nginx-pod namespace: default spec: containers: - name: nginx image: nginx volumeMounts: - name: nfs-volume mountPath: /usr/share/nginx/html volumes: - name: nfs-volume persistentVolumeClaim: claimName: pvc-nfs EOF # 查看Pod状态 $ kubectl get pods NAME READY STATUS RESTARTS AGE nginx-pod 1/1 Running 0 5m

# 创建StorageClass
$ kubectl apply -f – << EOF apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: nfs-storage provisioner: k8s.学习交流加群风哥微信: itpux-comio/nfs parameters: server: 192.168.1.100 path: /exports readOnly: "false" reclaimPolicy: Delete allowVolumeExpansion: true volumeBindingMode: Immediate EOF # 查看StorageClass $ kubectl get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE nfs-storage k8s.io/nfs Delete Immediate true 5m # 创建PVC $ kubectl apply -f - << EOF apiVersion: v1 kind: PersistentVolumeClaim metadata: name: pvc-dynamic namespace: default spec: accessModes: - ReadWriteMany resources: requests: storage: 5Gi storageClassName: nfs-storage EOF # 查看PVC状态 $ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE pvc-dynamic Bound pvc-12345678-1234-1234-1234-1234567890ab 5Gi RWX nfs-storage 5m # 查看PV状态 $ kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-12345678-1234-1234-1234-1234567890ab 5Gi RWX Delete Bound default/pvc-dynamic nfs-storage 5m

# 安装Ceph CSI插件
$ helm repo add ceph-csi https://ceph.github.io/csi-charts
$ helm install ceph-csi-rbd ceph-csi/ceph-csi-rbd –namespace ceph-csi

# 创建Ceph存储类
$ kubectl apply -f – << EOF apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: ceph-rbd provisioner: rbd.csi.ceph.com parameters: clusterID: ceph-cluster pool: kubernetes imageFeatures: layering csi.storage.k8s.io/provisioner-secret-name: ceph-secret csi.storage.k8s.io/provisioner-secret-namespace: ceph-csi csi.storage.k8s.io/controller-expand-secret-name: ceph-secret csi.storage.k8s.io/controller-expand-secret-namespace: ceph-csi csi.storage.k8s.io/node-stage-secret-name: ceph-secret csi.storage.k8s.io/node-stage-secret-namespace: ceph-csi reclaimPolicy: Delete allowVolumeExpansion: true volumeBindingMode: Immediate EOF # 查看存储类 $ kubectl get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE ceph-rbd rbd.csi.ceph.com Delete Immediate true 5m nfs-storage k8s.io/nfs Delete Immediate true 10m

# 安装Prometheus和Grafana
$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
$ helm install prometheus prometheus-community/kube-prometheus-stack

# 安装存储监控插件
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/rbac-snapshot-controller.yaml
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/setup-snapshot-controller.yaml

# 查看存储使用情况
$ kubectl top pod
NAME CPU(cores) MEMORY(bytes)
nginx-pod 1m 24Mi

# 查看PV使用情况
$ kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-12345678-1234-1234-1234-1234567890ab 5Gi RWX Delete Bound default/pvc-dynamic nfs-storage 10m

# 查看PVC使用情况
$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
pvc-dynamic Bound pvc-12345678-1234-1234-1234-1234567890ab 5Gi RWX nfs-storage 10m

# 案例：企业级NFS存储
# 环境：3节点K8s集群，1台NFS服务器
# 目标：部署NFS存储，为Pod提供共享存储

# 1. 配置NFS服务器
$ sudo dnf install -y nfs-utils
$ sudo mkdir -p /exports
$ sudo chmod 777 /exports
$ sudo echo “/exports 192.168.1.0/24(rw,sync,no_root_squash)” >> /etc/exports
$ sudo systemctl start nfs-server
$ sudo systemctl enable nfs-server

# 2. 安装NFS CSI插件
$ helm repo add nfs-subdir-external-provisioner https://ku学习交流加群风哥QQ113257174bernetes-sigs.github.io/nfs-subdir-external-provisioner/
$ helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner –set nfs.server=192.168.1.100 –set nfs.path=/exports

# 3. 创建StorageClass
$ kubectl apply -f – << EOF apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: nfs-client provisioner: k8s-sigs.io/nfs-subdir-external-provisioner parameters: pathPattern: {.PVC.namespace}/{.PVC.name} onDelete: delete reclaimPolicy: Delete allowVolumeExpansion: true volumeBindingMode: Immediate EOF # 4. 创建PVC $ kubectl create namespace fgedu-app $ kubectl apply -f - << EOF apiVersion: v1 kind: PersistentVolumeClaim metadata: name: app-storage namespace: fgedu-app spec: accessModes: - ReadWriteMany resources: requests: storage: 10Gi storageClassName: nfs-client EOF # 5. 部署应用 $ kubectl apply -f - << EOF apiVersion: apps/v1 kind: Deployment metadata: name: web-app namespace: fgedu-app spec: replicas: 3 selector: matchLabels: app: web-app template: metadata: labels: app: web-app spec: containers: - name: nginx image: nginx volumeMounts: - name: app-volume mountPath: /usr/share/nginx/html volumes: - name: app-volume persistentVolumeClaim: claimName: app-storage EOF # 6. 测试存储 $ kubectl exec -it web-app-6799fc88d8-2q4x2 -n fgedu-app -- bash -c "echo 'Hello from NFS storage' > /usr/share/nginx/html/index.html”
$ kubectl exec -it web-app-6799fc88d8-5b678 -n fgedu-app — cat /usr/share/nginx/html/index.html
Hello from NFS storage
$ curl http://$(kubectl get svc -n fgedu-app web-app -o jsonpath='{.spec.clusterIP}’)
Hello from NFS storage

# 案例：企业级Ceph存储
# 环境：5节点K8s集群，3节点Ceph集群
# 目标：部署Ceph存储，为Pod提供高性能存储

# 1. 部署Ceph集群
$ helm repo add rook-release https://charts.rook.io/release
$ helm install rook-ceph rook-release/rook-ceph –namespace rook-ceph –create-namespace
$ helm install rook-ceph-cluster rook-release/rook-ceph-cluster –namespace rook-ceph

# 2. 创建Ceph存储类
$ kubectl apply -f – << EOF apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: rook-ceph-block provisioner: rook-ceph.rbd.csi.ceph.com parameters: clusterID: rook-ceph pool: replicapool imageFormat: "2" imageFeatures: layering csi.storage.k8s.io/provisioner-secret-name: rook-csi-rbd-provisioner csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph csi.storage.k8s.io/controller-expand-secret-name: rook-csi-rbd-provisioner csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph csi.storage.k8s.io/node-stage-secret-name: rook-csi-rbd-node csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph reclaimPolicy: Delete allowVolumeExpansion: true volumeBindingMode: Immediate EOF # 3. 创建PVC $ kubectl create namespace fgedu-db $ kubectl apply -f - << EOF apiVersion: v1 kind: PersistentVolumeClaim metadata: name: mysql-storage namespace: fgedu-db spec: accessModes: - ReadWriteOnce resources: requests: storage: 50Gi storageClassName: rook-ceph-block EOF # 4. 部署MySQL $ kubectl apply -f - << EOF apiVersion: apps/v1 kind: Deployment metadata: name: mysql namespace: fgedu-db spec: replicas: 1 selector: matchLabels: app: mysql template: metadata: labels: app: mysql spec: containers: - name: mysql image: mysql:8.0 env: - name: MYSQL_ROOT_PASSWORD value: fgedu123 - name: MYSQL_DATABASE value: fgedudb - name: MYSQL_USER value: fgedu - name: MYSQL_PASSWORD value: fgedu123 volumeMounts: - name: mysql-volume mountPath: /var/lib/mysql volumes: - name: mysql-volume persistentVolumeClaim: claimName: mysql-storage EOF # 5. 测试存储 $ kubectl exec -it mysql-7d75c484b5-8x8x8 -n fgedu-db -- mysql -u fgedu -pfgedu123 -e "CREATE TABLE fgedu_test (id INT, name VARCHAR(255)); INSERT INTO fgedu_test VALUES (1, 'test'); SELECT * FROM fgedu_test;" +------+------+ | id | name | +------+------+ | 1 | test | +------+

# 案例：企业级本地存储
# 环境：3节点K8s集群
# 目标：部署本地存储，为Pod提供高性能存储

# 1. 安装本地存储插件
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/sig-storage-local-static-provisioner/master/deploy/kubernetes/example/default_example_storageclass.yaml
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/sig-storage-local-static-provisioner/master/deploy/kubernetes/example/provisioner_generated.yaml

# 2. 准备本地存储
$ sudo mkdir -p /mnt/disks
$ sudo mount /dev/sdb1 /mnt/disks
$ sudo chmod 777 /mnt/disks

# 3. 创建本地存储PV
$ kubectl apply -f – << EOF apiVersion: v1 kind: PersistentVolume metadata: name: local-pv labels: type: local spec: capacity: storage: 100Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Delete storageClassName: local-storage local: path: /mnt/disks nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - worker1 EOF # 4. 创建PVC $ kubectl create namespace fgedu-cache $ kubectl apply -f - << EOF apiVersion: v1 kind: PersistentVolumeClaim metadata: name: cache-storage namespace: fgedu-cache spec: accessModes: - ReadWriteOnce resources: requests: storage: 50Gi storageClassName: local-storage EOF # 5. 部署应用 $ kubectl apply -f - << EOF apiVersion: apps/v1 kind: Deployment metadata: name: redis namespace: fgedu-cache spec: replicas: 1 selector: matchLabels: app: redis template: metadata: labels: app: redis spec: containers: - name: redis image: redis volumeMounts: - name: redis-volume mountPath: /data volumes: - name: redis-volume persistentVolumeClaim: claimName: cache-storage EOF # 6. 测试存储 $ kubectl exec -it redis-7d75c484b5-8x8x8 -n fgedu-cache -- redis-cli set test "Hello from local storage" OK $ kubectl exec -it redis-7d75c484b5-8x8x8 -n fgedu-cache -- redis-cli get test "Hello from local storage"

# 常见问题与解决方案

## 1. PV创建失败
– 原因：存储后端不可用、权限问题、配置错误
– 解决方案：检查存储后端状态、检查权限配置、检查PV配置

## 2. PVC绑定失败
– 原因：没有可用的PV、PV与PVC不匹配、存储类配置错误
– 解决方案：创建足够的PV、确保PV与PVC匹配、检查存储类配置

## 3. 存储性能下降
– 原因：存储容量不足、I/O竞争、存储后端性能问题
– 解决方案：增加存储容量、优化应用I/O模式、升级存储后端

## 4. 存储数据丢失
– 原因：存储后端故障、数据未备份、PV回收策略错误
– 解决方案：使用高可用存储、定期备份数据、配置合适的回收策略

## 5. 存储扩展失败
– 原因：存储类不支持扩展、存储后端容量不足、权限问题
– 解决方案：使用支持扩展的存储类、确保存储后端有足够容量、检查权限配置