|
|
|
|
|
|
by clipradiowallet
1819 days ago
|
|
|
> I can't speak to the SRE side In all seriousness, what other side is there? The SRE's role is to make sure you never encounter kubernetes. eg... you have a git repo and some branches - if you push to them, deployments magically happen. As a non-SRE, what parts of kubernetes would you actually be touching or interacting with? |
|
|
In my org feature development teams own the K8S configuration and uptime for their own workloads/services.
The SRE team owns the shared Kubernetes platform itself and the related infra/config (cluster-level config, RBAC, the CI/CD infra, certificate tooling, the secrets infrastructure, the observability pipelines, etc).