The CircleCI release agent on K8s cluster requires which basically opts in management by the agent. This is not scalable for environments with matured DevOps infrastructure, where namespaces can be introduced, modified or torn down by individual developers in a quite dynamic fashion.

The situation would be eased by generating the list of namespaces to be managed by the CircleCI release agent with exception list. For example, if there's an option to specify like "please manage all namespace, except for kube-systems, default, etc", it'd become more scalable.