https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
yes. kube-proxy args are part of agent config which means it is per-node. Needs to be set individually on every node.
It is totally possible to run different nodes in different modes.
You’re disabling both CNI and cloud-controller, I assume you’re aware you need to replace those with something?
a
yeah i'm using Calico
and metallb
c
and what for your cloud provider?
a
hm its been a while since I originally came up with that command, can't remember now
i'm running this on-prem
i believe thats why i choose that option
c
a
i'm not seeing any options there, other than "use an external CCM"?
can I go back and enable the default?
isnt MetallB the load balancer in my case?
c
it is a loadbalancer yes, but you need all the other bits
you can just remove that flag from the server args
a
ok lemme try that
ok thanks for the help.. gotta troubleeshoot some routing issue now
s
aren't the 
cluster-cidr
and 
service-cidr
non-standard CIDR sizes?
c
yeah the ipv4 cluster-cidr won’t allow for more than a single node in the cluster if you’re using the built-in Kubernetes node IPAM since each node gets a /24… you’d need to reduce the node cidr mask or increase the total size of that cidr.
a
ok thank you.. going to rebuild
s
This is what I did in my test IPv4+IPv6 test cluster
Copy code
cluster-cidr: "10.1.0.0/16,fd30:cafe:1234:1::/56"
    service-cidr: "10.2.0.0/18,fd30:cafe:1234:2::/112"
a
thank you
Open in Slack
PreviousNext
Powered by