Considerations

Be watchful of your system’s resources usage

Your K3s Kubernetes cluster is not running “empty” at this point. It is already executing a number of services that eat up a good chunk of your hardware’s resources. Be always aware of the current resources usage in your setup before you deploy any new app or service in your cluster.

At this point of the guide, you can monitor the resource usages in your setup in these ways:

• The Proxmox VE’s web console has a Summary view on every level
  Datacenter, node and VMs have all a Summary page in which you can see the current resource usages.

• From the OS point of view, using shell commands like htop, free or df
  It is important that you also see the usage values from within your Proxmox VE host and VMs, because they are more fine grained and can indicate you better how resources are being used.

• The kubectl top command
  Gives you the view on resources usage from within your K3s cluster.

• Headlamp
  The Headlamp dashboard you deployed previously offers a resources usage overview in its main Clusters page.

Do not fill your cluster up to the brim

Just because you still have free RAM or a not so high CPU usage, it does not mean that you can keep on deploying more services in your setup. You must leave some room for possible usage spikes, and for the underlying platforms running everything (Proxmox VE and K3s) which also need resources to run. This way you can run sporadic tasks like backup jobs or updates when required.