Merge pull request #2974 from faweizhao26/case

add one new case logo
This commit is contained in:
KubeSphere CI Bot 2023-09-07 16:02:06 +08:00 committed by GitHub
commit 8f0c35a000
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 1 deletions

View File

@ -164,6 +164,8 @@ section3:
icon: '/images/case/logo-yiheda.png'
- name: 'bobinfo'
icon: '/images/case/logo-hsh.png'
- name: 'yf5g'
icon: '/images/case/yf5g-logo.png'
- name: 'Energy'
children:

View File

@ -52,7 +52,7 @@ $ kubectl -n kubesphere-logging-system get pvc data-elasticsearch-logging-data-1
## 复制数据
不管 PV 的 accessModes 是 [ReadWriteOnce](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) 还是 [ReadWriteMany](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes),在复制数据之前都要将应用的副本数量缩减为 0因为 ReadWriteOne 模式同时只允许挂载一个 Pod新 Pod 无法挂载,而 ReadWriteMany 模式如果不将副本数量缩减为 0在复制数据时可能会有新的数据写入。所以无论如何,都要将副本数量缩为 0 。
不管 PV 的 accessModes 是 [ReadWriteOnce](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) 还是 [ReadWriteMany](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes),在复制数据之前都要将应用的副本数量缩减为 0在复制数据时可能会有新的数据写入。所以无论如何都要将副本数量缩为 0 。
```bash
$ kubectl -n kubesphere-logging-system get sts

View File

@ -240,6 +240,8 @@ section3:
icon: '/images/case/logo-yiheda.png'
- name: 'bobinfo'
icon: '/images/case/logo-hsh.png'
- name: 'yf5g'
icon: '/images/case/yf5g-logo.png'
- name: '能源'
children:

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB