++blog
This commit is contained in:
parent
827b24bfd8
commit
c61af0220e
1 changed files with 23 additions and 0 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue