How to keep Kubernetes RBAC and audit logs consistent across STACKIT, IONOS and a hyperscaler
Blog post from Qovery
Kubernetes access and audit logging differ across STACKIT, IONOS, EKS, GKE and AKS, despite their shared support for standard Kubernetes RBAC: STACKIT supports federated sign-in but its API-server audit forwarding remains in Private Preview, while IONOS can send audit logs to Object Storage but has no documented OIDC sign-in path for the Kubernetes API; the hyperscalers support identity-provider integration and provider-specific logging services, generally requiring audit settings to be enabled. To create a consistent model, the guide recommends using one identity provider, mapping its groups to provider-specific RBAC subjects, storing shared roles and bindings in Git, applying them with Argo CD or Flux, and enforcing policy with Kyverno or OPA Gatekeeper. It also advises sending each provider’s audit stream to a central system and normalizing event fields, while testing IONOS log formats and accounting for STACKIT’s preview status. An authentication proxy such as Pinniped can provide per-user identity for IONOS, and administrative credentials should be restricted to break-glass use. Qovery can standardize access and record deployment and configuration actions made through its platform, but it does not combine clusters’ Kubernetes API audit logs, which organizations must collect separately.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Kubernetes | 74 | 3,388 | 294 | 94 | -34% |
| Platform Engineering | 32 | 1,080 | 220 | 61 | -46% |
| MCP | 10 | 7,404 | 711 | 183 | -38% |
| AI Agents | 4 | 4,689 | 923 | 218 | -33% |
| Secrets Management | 3 | 1,990 | 378 | 124 | -36% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.