This message was deleted.
# k3s
a
This message was deleted.
h
I think it would be better if you ask specific question on where you are stuck and / or where you are having problem in the process?
🎯 2
j
I am not able to setup K3s cluster, Like where to start from , what steps to follow? I didnt find any simple and easy to understand doc to follow to setup 3-node multi master k3s cluster.
h
If you want to use embedded etcd this is an easy doc to deploy 3-node HA k3s cluster: https://docs.k3s.io/datastore/ha-embedded?_highlight=high If you want to use external DB (see cluster datastore requirement in step 1) this is the doc: https://docs.k3s.io/datastore/ha
Also check the requirements page for k3s - https://docs.k3s.io/installation/requirements If Rancher is going to be in the mix then also review the support matrix to make sure you are running supported k3s version and OS release https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-9/
l
Maybe even start with k3d or kind to get an understanding on Kubernetes in general.
đź’Ż 1
j
Could anyone is there who can connect over a video call to discuss the architecture. I request to spare some time for me; I will also document it and make a video on it for community !
l
You’re kinda asking a lot here. People are on here pro-bono mostly. It’s not clear what you’ve already tried. And did you read the blog posts? There’s simply sooo much info out there on how to setup K3s and Kubernetes in general. So rather quickly you should be able to determine a minimum set of required things you need to do.
Is this a personal project or business?
j
Its for my organization !
l
Okay … and nobody in your org. can help. You’re alone on a business project likely to host important business applications?
Please Sir. When the community is to advice you on this rather big scope. Then: • In general go in this direction:
I think it would be better if you ask specific question on where you are stuck and / or where you are having problem in the process?
as Mr. @hundreds-evening-84071 stated • read the blog posts that we point you towards • state what you’ve already: > tried > where you’re potentially stuck > what errors you’re seeing > versions and what not … use e.g. Gist for longer/detailed info/logs and that kind General architecture advice and guidance on designing a cluster is available in soooo many guides, official K8s and K3s docs .. state what you’ve followed and read. Such guidance and previous “how did we do this” is available in video on YouTube. --- The scope here is something that a ton of consultancy companies provide and if this project have any value to your company they should provide you with a minimum of resources so that you can deliver a proper solution.
I’m willing to help. There’s a balance to things and scope though.
j
Okay I will get back to you soon !!
l
Hello @jolly-baker-4168, good day! This is just to remind you that while the community is here to support your queries, please do not mistake it for paid customer support. We're happy to help guide you to the right docs/resources. However, if you need someone to connect over a call and assist you with your very specific use case, that would be within the remit of paid support. In case you're interested in exploring the option, please check out the link here.
âś… 1
🎯 2
👍 1
j
1. My Requirement is to setup a 3-node K3s server cluster with embedded etcd datastore. For that I am consolidating the network and hardware resources. I have gone through the reference link of K3s, and drawn following conclusions.Kindly confirm me whether I am correct with it or any modifications to be done ?? Hardware: (Per Node) CPU: 2 core RAM: 2 GB Networking: 1. all devices or computers in the network should be able to reach and communicate with the K3s server using the specified port (6443). 2. The nodes need to be able to reach other nodes over UDP port 8472 when using the Flannel VXLAN backend. 3. The nodes should not listen on any other port. 4. For achieving high availability with embedded etcd, server nodes must be accessible to each other on ports 2379 and 2380. Note: The VXLAN port on nodes should run behind a firewall/security group that disables access to port 8472 to outside world. With respect to our requirement, Inbound Rules for K3s Server Nodes: ProtocolPortSource DestinationDescriptionTCP2379-2380 Servers Servers Required only for HA with embedded etcdTCP 6443 Agents Servers K3s supervisor and Kubernetes API ServerUDP 8472 All nodes All nodes Required only for Flannel VXLAN
l
Can you please fix the syntax on your latest message … very cumbersome to read. My first response is though, that’s too few resources for the control-planes.