Skip to content

2025

Dynamically configuring RBAC for CD workflows

Handling RBAC (Role-Based Access Control) in Kubernetes can be challenging, especially when you need to dynamically configure permissions for CD tools that use Service Accounts (SAs) across multiple namespaces. We will explore how to configure dynamic RBAC in a real world scenario, taking ArgoCD as an example configuring the necessary permissions for its Service Account in each namespace. This approach can be adapted to other CD tools like FluxCD or Jenkins.

KubeNSync when using Cluster API

When managing multiple Kubernetes clusters, using Cluster API (CAPI) for deploying, and ArgoCD, FluxCD or similar tools for deploying applications, is a common scenario. However, managing basic cluster configuration such as CCMs, Pull Secrets, etc. can be hard to manage.

In these cases, using tools like ClusterResourceSet (CRS) or the Helm chart provider can help, but they often require additional steps like building the Helm values, injecting secrets, and potentially depending on external tools like some kind of vault.