Properly is the keyword here. Not everyone understands that the masters need to be HA. People have been given the assumption that Kubernetes provides HA to your entire stack. Which by all means it can, It can do it really well. However, the master needs to be setup with HA. Which by default many are not.
For example:
As such places are providing single master nodes in regards to Kubernetes and they are and can become a single point of failure.
Further, most guides on Kubernetes do not provide HA for the master. The master is left as a single and as such, it is a single point of failure in your cluster. You can lose a whole worker node, and the master will work on redeploying the pods to another worker. If you lose the only master other wonkyness will occur. Like in my case nginx-ingress just stopped handling requests because it didn’t know where to route the requests in the backend.
So with that knowledge… my statement is accurate.
… unless you make the master highly available.