netmaker
- j
jolly-london-20127
10/13/2021, 11:36 AMIt’s meant for PoC testing installs. For production installs your own domain can be used. However, it’s a free DNS service that will just return an IP based on several regex patterns. So basically you can have https dns for any ip without needing to configure a dns provider - i
incalculable-musician-80046
10/13/2021, 12:41 PM@User something still nmnot right with routes on both fedora and debian - i
incalculable-musician-80046
10/13/2021, 12:41 PMif i set an egress for 0.0.0.0/0 seems nothing switches my default route - i
incalculable-musician-80046
10/13/2021, 12:42 PMnetstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 enp1s0 10.11.12.0 0.0.0.0 255.255.255.0 U 0 0 0 nm-Optim - i
incalculable-musician-80046
10/13/2021, 12:42 PMwhere i would think the gateway should be nm-Optim - s
straight-lock-3524
10/13/2021, 1:01 PMThat I said before 🙂 - s
straight-lock-3524
10/13/2021, 1:02 PMhaven't gotten it to work as it should either - g
gray-caravan-67799
10/13/2021, 7:17 PMman... it's been a minute since I reset netmaker back up from scratch. Those docs are the tits, and everything was super fluid. - g
gray-caravan-67799
10/13/2021, 7:17 PMI think I might be having some coreDNS issues... but nothing that stopped the primary functionality. - s
straight-lock-3524
10/13/2021, 7:29 PMnice - m
microscopic-room-14967
10/18/2021, 9:06 PMhi, i saw read some cool updates to netmaker and thought i would update my netmaker config and figure out whats new - m
microscopic-room-14967
10/18/2021, 9:06 PMi was using netmaker v0.5 as a flannel underlay, then installing k3s on top of that by setting the
optionflannel-iface - m
microscopic-room-14967
10/18/2021, 9:07 PMwith the new kubernetes topologies, are you saying i dont need to setup netmaker as an underlay first? - j
jolly-london-20127
10/18/2021, 9:08 PMhi @User , that depends on what you want to do - j
jolly-london-20127
10/18/2021, 9:08 PMif you are using it to build a distributed cluster, then you probably need to deploy it first - j
jolly-london-20127
10/18/2021, 9:08 PMif you want to connect clusters in different locations, then you can deploy it on top - m
microscopic-room-14967
10/18/2021, 9:09 PMah ok, i think i need it as an underlay then - j
jolly-london-20127
10/18/2021, 9:09 PMyeah, from what I've been able to tell, there's not a good way to get around needing the network first. I think there's some real hack-y stuff you can do post-deployment to change the networking but you probably dont want to do that - j
jolly-london-20127
10/18/2021, 9:09 PMhowever - j
jolly-london-20127
10/18/2021, 9:10 PMyou can change the management of the cluster to be within the cluster, after it's been deployed, if that makes sense - j
jolly-london-20127
10/18/2021, 9:10 PMthat's what we do in the MicroK8s tutorial - m
microscopic-room-14967
10/18/2021, 9:10 PMyeah, i'm happy to do it as an underlay - i just wanted to check i wasnt missing a trick, as i really like the k8s way of deploying and managing stuff - j
jolly-london-20127
10/18/2021, 9:11 PMso, you can do something similar to the microk8s tutorial, where you first deploy the client standalone, and then deploy the daemonset afterwards, which will "take over" the client - m
microscopic-room-14967
10/18/2021, 9:11 PMi read the microk8s tutorial - but i wasnt too keen on the idea of having the control plane on every node essentially. maybe its a bias i need to get rid of though - j
jolly-london-20127
10/18/2021, 9:11 PMyou can do the same with k3s - j
jolly-london-20127
10/18/2021, 9:11 PMwithout the control plane part - j
jolly-london-20127
10/18/2021, 9:11 PMhowever - j
jolly-london-20127
10/18/2021, 9:12 PMin my testing, it's better to have the client management outside of the cluster anyway - j
jolly-london-20127
10/18/2021, 9:12 PMreason being: the netclient provides the underlay for all the pod networking - j
jolly-london-20127
10/18/2021, 9:12 PMso lets say something goes wrong with your cluster