Remix.run Logo
tombert 3 months ago

If I had set up the infrastructure myself I'd probably have a different opinion on all of this stuff, but I came into this job where everything was set up for me. I don't know if it was don't "incorrectly", and I do fear that stating as such might get into territory adjacent to the "no true Scotsman" fallacy.

I mostly just think that k8s integration with GCP is a huge pain in the ass, every time I have to touch it it's the worst part of me day.

fragmede 3 months ago | parent [-]

What about your integration makes it a huge pita?

tombert 3 months ago | parent [-]

It's just a lot of stuff; we have a couple hundred services, and when I've had to add shit, it ends up with me updating like two hundred files.

Infrastructure as code is great, but lets be honest, most people are not thoroughly reading through a PR with 200+ files.

There's of course tpl files to help reduce duplication, and I'm grateful for that stuff when I can get it, but for one reason or another, I can't always do that.

It's also not always clear to me which YAML corresponds to which service, though I think that might be more of an issue with our individual setup.

fragmede 3 months ago | parent [-]

Yeah ew sounds like a mess. I'm sorry, thanks for sharing. Death by a thousand paper cuts is never fun. The solution in looking at for my problem in this area is to add another layer of indirection and make a config generator so that there's only one config file for users to define their service in, and the program goes off and makes all the necessary changes to the pile of yaml files.