Why should I care? This piece will be useful to you if you need to ensure that workloads in your cluster don’t have cluster-scoped access to resources, even if they are controllers that one would typically consider closer to the control plane than to individual workloads. You are probably looking for ways to configure external secrets management with namespace isolation or more specifically how to configure ESO (External Secrets Operator – external-secrets) through a namespaced approach.
We’re excited to announce the launch of our Free-tier! With it, you can leverage the External Secrets Inc. Agent to manage deployments of the External Secrets Operator, streamlining secrets management across your cloud-native infrastructure. Our platform includes: Enterprise Distribution of External Secrets Operator: Pre-configured with enterprise-exclusive providers. Automatic Image Updates: Ensure your deployments stay up-to-date with configurable policies for image management. Namespace and Cluster Scope Management without RBAC Hassle: Easily control and monitor ExternalSecretsOperator deployments without complicated RBAC configurations.