kubeadm VS kubescape

It works on top of KubeADM, you can also implement specific configuration about it.

https://github.com/kubernetes/kubeadm/blob/main/docs/ha-considerations.md was a huge help in getting it up and running.

Kubeadm is a more barebones tool, focusing on cluster node setup and Kubernetes component installation. It’s a command line tool that facilitates the various setup operations, but configuration needs to be done manually and per node.

For HA I opted for keepalived + haproxy and it has been working quite well so far (followed the guide from https://github.com/kubernetes/kubeadm/blob/main/docs/ha-considerations.md)

- set up with a Load Balancer (I'm using haproxy)

This is a useful guide on how to set them up (note: the version of HAProxy they specify is no longer being maintained, but you can upgrade it to a later version): Kubeadm - HA Considerations

Hi, last few days I'm solving the same thing. So I found some helpful github issue https://github.com/kubernetes/kubeadm/issues/581 maybe it helps.

Kubeadm is a cluster provisioning tool implementing the best-practices for creating Kubernetes clusters (following Kubernetes The Hard Way steps). Kubeadm performs the actions necessary to get a minimum viable and secure cluster. It follows Kubernetes operator architectural approach for cluster creation and management. What is also important, Kubeadm is an official Kubernetes SIG Lifecycle project - this is important because official Kubernetes SIG projects usually tent to have better community support and be more mature than their non-official counterparts.

In this article, we'll learn how to run Kubescape in our CI/CD pipelines to detect threats before they are deployed.

Use tool like Kube-hunter, Popeye and Kubescape for security weaknesses and misconfigurations in kubernetes clusters and visibility of security issues.

The Kubescape CLI, which you can find here.