Been working with go for over 5 years now, I dread every time I have to touch a project with anything related to k8s. Don't get me wrong, I think it's great what they have accomplished project wise, but what a complete mess code wise.
I don't get it I thought k8s was like the perfect match for Go? K8s is even written in Go. I know that doesn't strictly mean it must be easy to use Go, but it seems weird that it wouldn't be K8s best experience.
It has a reputation for being terrible Go code.
My read is that it just go too big and they didn't do a great job of keeping up with golang. Last I looked it was still not module compatible fully.
It actually started as a Java project until the team got some strong advocates.
The post is referring to the codebase of k8s itself, not the experience of deploying go code to k8s.