From c61af0220e1ef14724c79dd225ff5542fbbd0d0b Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Sat, 3 Sep 2022 15:33:15 +0200 Subject: [PATCH] ++blog --- .../contents.lr | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/content/u/blog/2022-08-27-migrating-ceph-nautilus-into-kubernetes-with-rook/contents.lr b/content/u/blog/2022-08-27-migrating-ceph-nautilus-into-kubernetes-with-rook/contents.lr index 4e9e381..1de8aaf 100644 --- a/content/u/blog/2022-08-27-migrating-ceph-nautilus-into-kubernetes-with-rook/contents.lr +++ b/content/u/blog/2022-08-27-migrating-ceph-nautilus-into-kubernetes-with-rook/contents.lr @@ -312,9 +312,32 @@ To see the stack trace of this error execute with --v=5 or higher [00:16] server57.place5:~# ``` +### Networking 2022-09-03 + +* Instead of trying to merge the cluster networks, we will use + separate ranges +* According to the [ceph users mailing list + discussion](https://www.spinics.net/lists/ceph-users/msg73421.html) + it is actually not necessary for mons/osds to be in the same + network. In fact, we might be able to remove these settings + completely. + +So today we start with + +* podSubnet: 2a0a:e5c0:0:14::/64 +* serviceSubnet: 2a0a:e5c0:0:15::/108 + +Using BGP and calico, the kubernetes cluster is setup "as usual" (for +ungleich terms). + + ## Changelog +### 2022-09-03 + +* Next try starting for migration + ### 2022-08-29 * Added kubernetes/kubeadm bootstrap issue