Dario Tranchitella

> is there a way to target or exclude individual namespaces for the additionalMetadata property in capsule? No, there's no chance of achieving this. This is definitely a very subtle...

I'm reopening this just to allow people to comment on it and share their interest in this feature.

Thanks for opening this, @adabuleanu. I'll try to rise a PR to solve this, it would be great if you could give it a try!

@adabuleanu I'm testing this by running Capsule v0.5.0 (`ghcr.io/projectcapsule/capsule:v0.5.0`) but I'm not able to replicate the issue. ``` $: kubectl get tnt dummytenant -o yaml apiVersion: capsule.clastix.io/v1beta2 kind: Tenant metadata:...

I would postpone this change for v0.6.0 since the upcoming one (v0.5.0) is already adding some fields. We could take advantage of the new API version that will provide `podOptions`...

Thanks for opening this feature request, @Lennie! Of course, this feature is definitely interesting for the multi-tenancy scope, and Capsule aims to cover the use-cases. [If I understood correctly](https://kubernetes.io/blog/2023/09/13/userns-alpha/#what-s-next), v1.29...

I like the idea of automating the deployment of the `kubeconfig`. Since we're talking about the `capsule-proxy`, BTW, I think this should be delegated to that project, since without it...

> It does not appear correct to grant a standard user access to update finalizers on a cluster-scoped resource. Couldn't we solve that with the `resourceNames` key? It grants the...

> Why must Capsule set Tenant as the Namespace **controller**? Would it be sufficient to set it as an owner? There's a subtle but essential difference between OwnerReference and ControllerReference....

Removing this issue from the v0.3.4 milestone since there's no support offered by the reporter and we (as maintainers) don't have the chance to test this functionally with a real...