u/Belladonna2278

now it feels like the cloud resources themselves aren’t even the difficult part anymore.

it is more the project structure, IAM permissions, shared VPC setup, service accounts and trying to figure out where things are supposed to live long term once more teams start getting involved.

everything usually makes sense when it is first set up

but months later even small changes turn into digging through old docs, tickets and permission chains trying to understand why something was configured a certain way in the first place.

starting to feel like the organizational side of GCP scales faster than the infrastructure itself sometimes.

random pipelines alert rules permissions temporary fixes that turned into permanent infrastructure without fanfare

everything was fine until one little thing broke and then all of a sudden nobody remembers why something was set up that way to begin with

then it is a matter of digging through old tickets and old docs to try to piece together the original logic

[ Removed by Reddit on account of violating the content policy. ]

[ Removed by Reddit on account of violating the content policy. ]

now it feels like our infrastructure work is growing faster than the actual product.

We moved deeper into Kubernetes and managed cloud expecting things to get easier operationally over time but it is been kind of the opposite. The cluster itself is not even the main issue anymore it is everything around it.

Monitoring, logging, networking, ingress, security tooling, observability costs, random AWS surprises it all adds up fast.

At some point we realized we were spending more engineering time managing infrastructure behavior than building features.

Curious if other teams hit a similar wall after scaling Kubernetes a bit further into production?