4 ms·
> K3S is for orchestration across nodes, and by design you can't run services on the master for security reasons unless you manually change it. That has not be
by tarruda 3y ago
> K3S is for orchestration across nodes, and by design you can't run services on the master for security reasons unless you manually change it.
That has not been my experience with k3s. Unlike normal distributions, k3s servers do allow workload to run on them unless you manually disable. From https://docs.k3s.io/datastore/ha-embedded https://docs.k3s.io/datastore/ha-embedded :
"
An HA K3s cluster with embedded etcd is composed of:
- Three or more server nodes that will serve the Kubernetes API and run other control plane services, as well as host the embedded etcd datastore.
- Optional: Zero or more agent nodes that are designated to run your apps and services
"
So you can have a full HA k3s cluster with only 3 server nodes and 0 agent(worker) nodes.
- sleepybrett 3y agoThis is not true of k8s in general, maybe certain on prem 'distributions' enforce this, i'm not sure. Sometimes kubernetes admins/operators who are running their own control planes and etcd will run etcd on non k8s controlled nodes, or they will run it on the same nodes that run their control plane services (scheduler, apiserver, controller manager, etc). Often those nodes will be tainted in such a way that they don't get overloaded by a noisy neighbor 'customer pod', but that's in no way 'by design'.. perhaps by convention or best practice.
- deleted 3y ago[deleted]
- worksonmine 3y agoYeah, design was probably a poor choice of words, s/design/default/.
- worksonmine 3y agoYes, you can ignore the warnings and change the defaults, like I said? > unless you manually change it I ran into this myself just the other day.