Don't maintain the cluster. Have someone else run it for you. Unless you want K8s cluster to be the only thing you do. The advantage of K8s is that it abstract

Don't maintain the cluster. Have someone else run it for you. Unless you want K8s cluster to be the only thing you do. The advantage of K8s is that it abstracts so much away from you, that you should (in theory) be able to take the same YAML config file from AWS EKS to GCP GKE to Azure AKS...and it runs the same everywhere. Things like loadbalancering and HTTP ingress rules that normally would manual configs on each platform - become part of the K8s config.