> You also had a pentest of your setup so you are perfectly sure you don't expose something to the internet that you are not supposed to? What are you talking

> You also had a pentest of your setup so you are perfectly sure you don't expose something to the internet that you are not supposed to? What are you talking about? With Kubernetes you need to explicitly expose something. In code. And apply that change. And see it explicitly listed in the descriptions. Outside of Kubernetes, you're already talking about a requirement that applies to all web services, regardless of deployment solution. Why didn't you mentioned that? > You also considered updates for Ubuntu and microk8s so you have strategy for updating your nodes with newer versions and security patches. What point were you trying to make? Do you believe Kubernetes is the only software that requires updating? Even so, with Kubernetes you can launch a freshly created instance in your cloud provider of choice, add it to the cluster, and go on with your day. If you'd want, you can drain a node, shut it down, and rebuild the node from scratch. Where exactly do you see a challenge?