ungleich-public/ungleich-staticcms
6
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

blog: update w/ k8s incompatibility

Browse source
This commit is contained in:
Nico Schottelius 2023-05-18 13:01:50 +02:00
parent 981181daa7
commit 81a96547b3
1 changed files with 15 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
content/u/blog/2022-08-27-migrating-ceph-nautilus-into-kubernetes-with-rook/contents.lr
View file

@ -609,8 +609,7 @@ printed in its logs:
``` ```
So we need to downgrade to rook v1.7. Using `helm search repo So we need to downgrade to rook v1.7. Using `helm search repo
rook/rook-ceph --versions` we identify the latest usable version rook/rook-ceph --versions` we identify the latest usable version should be `v1.7.11`.
should be `v1.7.11`.
We start the downgrade process using We start the downgrade process using
@ -794,7 +793,7 @@ join our existing cluster.
### Checking the toolbox and monitor pods for migration ### Checking the toolbox and monitor pods for migration
When the ceph-toolbox is deployed, we get a ceph.conf and a keyring in When the ceph-toolbox is deployed, we get a ceph.conf and a keyring in
/ect/ceph. The keyring is actually the admin keyring and allows us to /etc/ceph. The keyring is actually the admin keyring and allows us to
make modifications to the ceph cluster. The ceph.conf points to the make modifications to the ceph cluster. The ceph.conf points to the
monitors and does not contain an fsid. monitors and does not contain an fsid.
@ -834,7 +833,7 @@ kubectl -n rook-ceph patch deployment rook-ceph-mon-$mon --type='json' -p '[{"o
done done
``` ```
No the pod is restarted and when we execute into it, we will see that Now the pod is restarted and when we execute into it, we will see that
no monitor is running in it: no monitor is running in it:
``` ```
@ -1185,6 +1184,18 @@ references to the monitors, this problem might repeat.
## Changelog ## Changelog
### 2023-05-18
* rook 1.7.11 does not work on kubernetes 1.26.1 anymore
* PodSecurityPolicy is missing
```
The Kubernetes API could not find policy/PodSecurityPolicy for
requested resource rook-ceph/00-rook-ceph-operator. Make sure the
"PodSecurityPolicy" CRD is installed on the destination cluster.
```
### 2022-09-10 ### 2022-09-10
* Added missing monitor description * Added missing monitor description