Jump to content

How many pods can be opened in k3s(lightweight kubernetes)?


Go to solution Solved by requinix,

Recommended Posts

k3s is a simplified version of k8s, not a trial version. You can have as many pods as you have resources for, and "resources" includes IP addressing space. But IP addresses depends on your networking setup, which can be anything from a tiny 192.168 IPv4 space to a massive IPv6 range, to even multiple CIDRs.

Were they trying to get a specific number? Because my answer would have been "as many as you want".

  • Solution

Because there are only a finite number of IP addresses in a CIDR, and you "have" to allocate a CIDR to be used for pod networking. If you have so many pods that you run out of available IP addresses, any more pods won't be able to run.

It's not a great question, because it's a matter both of IP addressing, configuration and defaults.  For one node, the configured limitation is 110 pods, which is fewer than what is available in a /24, but can be reconfigured.

What is the question supposed to do?

Is the question supposed to test if the interviewee knows about the 110 pods/host limit? Then you ask a question like "How many pods can k3s run on a host?"
Is the question supposed to test if they know about Kubernetes networking and about pod and cluster IP addresses? Then you ask a detailed question like "If a k3s network is configured to use the entire 192.168 subnet for pod networking, how many pods will be able to run?"

Is the question supposed to be a trick question, meaning it is supposed to confuse and disorient the interviewee? Then don't ask it. Because asking trick questions in interviews is an indicator of abusive management and poor leadership.

Often these types of questions are vague and missing in information in order to see if you have an understanding of K3s.  

A much more direct and useful question would be:  "Are you familiar with K3s, and why would you use it instead of a K8 implementation?"

At that point, you'd want to be able to talk about why K3 was created, how it differs from K8 implementations, and where you might use it or not.  

Answers to those questions are summarized very well here:  https://traefik.io/glossary/k3s-explained

K3 was a project from Rancher Labs, which was acquired by SUSE, so check out https://www.rancher.com/ if you want to find more resources for K3s and see how it fits into the Rancher suite of products.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.