Yeah this stuff is hilarious and sad. I'm in the middle of setting up a kubernetes cluster for a relatively big company. K8s in their environment makes sense.

Yeah this stuff is hilarious and sad. I'm in the middle of setting up a kubernetes cluster for a relatively big company. K8s in their environment makes sense. However, the first conversation (after finishing up the contract) with the sysadmins went like: "Yeah, ingresses are fine and such, but we'll have our loadbalancer in front of that which will inspect the url paths to know which ingress it has to go to, we don't want some 'developer' to open up some new endpoint without us approving it! Those guys never know what they're doing." At this point I'm not sure if he's pulling my leg or something, b/c before the we wrote up the contract the whole idea was to give their dedicated platform team and developers more self service. In one fell swoop, bam, negated. Devops imo is about clear responsibility, it just doesn't work if boundaries are not communicated explicitly. In the above scenario once everything is setup, developers will not gain any velocity, and the sysadmin are still manually adding url routing to their loadbalancers.