Dario Tranchitella

Thanks for sharing these requirements but I'm not still understanding them properly. As @bsctl said,m since Capsule is (ab)using underlying Kubernetes primitives, most of the actions can be performed using...

Thanks for all the useful insights, as I said, really appreciated it. Although these features could be useful to onboard users with the Capsule domain logic, we are already focusing...

/assign @droot

Thanks for opening a feature request @dirien, I appreciated that! It required a bit of time to consider this feature, and I wanted to investigate a bit, and my assumptions...

Exactly, keep in mind we're using Operator SDK along with Kubebuilder annotations that allow us to scaffold and generate the required code, as mentioned [here](https://book.kubebuilder.io/reference/generating-crd.html#scale). Further details on the purpose...

@arriqaaq may I help you with this? I'd like to release the new version and this would be absolutely helpful, in case you're not available in contributing to this, please,...

> one or more Tenant Node Pools (TNPs) running in isolated networks and joined with the TCP Just for the sake of clarity: the Cluster API provider will reconcile only...

> Since topology constraints are specific of the admin cluster hosting the `tcp` and not of the specific `tcp`, this seems a more wise option. This would be applied to...

> ```yaml > spec: > topologySpreadConstraints: > - maxSkew: 1 > topologyKey: topology.kubernetes.io/zone > whenUnsatisfiable: DoNotSchedule > labelSelector: > matchLabels: > app: tcp > ``` Question on this: the `matchLabels`...

I think the feature is precious, I'm just saying that when deploying a Tenant Control Plane the Cluster Administrator should know in advance the Pod labels used because otherwise, the...