I've been dragging me feet on implementing k8s, suspecting that its complexity would eventually be reduced by its evolution.
And then a couple weeks ago, I was tasked with standing up a new Ansible AWX server, which now done via a k8s operator. It was an exquisitely painful experience. This is potentially a bad example because I'm pretty sure IBM's plan with AWX is now to make me suffer, but through that entire process, k8s just felt like extreme overkill.
I'm pretty sure that's going to be the last time I use k8s. I know it makes sense for some use cases, but I it just doesn't feel intuitive in any way. And although it may seem more efficient, I absolutely dread having to troubleshoot any problems down the road.
I'm probably not the target audience, but thought I'd leave a comment for fun anyway.
Can you share more about your awx-operator and/or k78s pains? I was tinkering with it this weekend and I'd like to compare notes. I got the basic install via kustomize working just now, because I got stuck with the helm-based method.
And then a couple weeks ago, I was tasked with standing up a new Ansible AWX server, which now done via a k8s operator. It was an exquisitely painful experience. This is potentially a bad example because I'm pretty sure IBM's plan with AWX is now to make me suffer, but through that entire process, k8s just felt like extreme overkill.
I'm pretty sure that's going to be the last time I use k8s. I know it makes sense for some use cases, but I it just doesn't feel intuitive in any way. And although it may seem more efficient, I absolutely dread having to troubleshoot any problems down the road.
I'm probably not the target audience, but thought I'd leave a comment for fun anyway.