I like k8s but this is way too optimistic.
I regularly run long-standing 20+ instance clusters using boto, pip, and a few hundred lines of python scripts. People have been doing some version of this for ~15 years.
K8s adds a lot of conceptual overhead on top of "just write a sysadmin script". It is absolutely not necessary to have an orchestration system as soon as you're past one instance.
It depends, of Course on aws stuff is a little Bit easier, especially zero downtime deployments. But thats not the case in on premise Environments
- automation - configuration management - scheduling - load balancing - provisioning
you can than either built it yourself, probably with the help of ansible/puppet,... or you can just use kubespray+k8s or any other "managed" k8s thingy.
of course if you try to manage more than 1 server you at least need some understanding of networking (but probably not that deep than you think), understanding of namepsaces or virtualisation (unless you think it's a good idea to run 1000 tools on one host without at least limit their cpu/memory/io usage) and you probably need knowledge of linux and also at least a little bit of knowing how distributed leader election might work. But no matter what, if you run more than one system you need to have somebody that is capable of that.