- using ping
- sshing into a box
- using ssh port forwarding
- using ps aux
- understanding system load
- understanding oom killer messages
- is this systemd? use systemctl, otherwise figure it out
- is this systemd? use journalctl, otherwise figure out where an app is logging
- is nginx running? what box is it running on?
- is the nginx config okay?
- what about haproxy? are health checks going through?
Plus dealing with whatever configuration management system you're using, credential store you're using, etc.
Kubernetes, while complex, does take over a huge chunk of responsibilities from existing deployments. As such, a large part of any debugging will be done via kubectl and on a much different level of abstraction than if you were dealing with individual machines and services deployed on them via Ansible.
Yes, there's new things to learn. But for many cases (not even just scale!) it's quite worth it.
For those that do need a solution like Kubernetes, charts like this are helpful, and the knowledge requirements certainly aren't too steep relative to comparable platforms.
What about Kubernetes makes it especially worth going in and commenting that you don't have a use case for it, in a thread dedicated to Kubernetes? Would you make similar comments about other platforms/libraries/technologies that you, for whatever reason, don't have a use case for?