After creating a new TCP (jonny-dev), the Kamaji controller is trying to get the address of the (Tenant Control Plane) / service. Because the service is not ready yet, this will result in the error cannot retrieve Service for the TenantControlPlane: Service \"jonny-dev\" not found.

Additionally, the controller is trying to update the resource (error applying TenantcontrolPlane status: cannot retrieve Service for the TenantControlPlane: Service \"jonny-dev\" not found) and is trying to reconcile the resource (error applying TenantcontrolPlane status: cannot retrieve Service for the TenantControlPlane: Service \"jonny-dev\" not found).

After this we get the error, that the service is running but the Service resource is not yet exposed as LoadBalancer (error applying TenantcontrolPlane status: cannot retrieve the TenantControlPlane address, Service resource is not yet exposed as LoadBalancer). This happens each second until the service is exposed to a LoadBalancer.

After this the flow is working as expected. This all happened in 5 seconds (2025-01-10T14:46:32Z > 2025-01-10T14:46:37Z). We are watching pods for "ERROR" logs to check if there are problems with the connection to the database of whatever. This seems more like a "Polling"-thing that's expected to fail for a few trys without that much error output.

I've attached the TCP.log of the dev-instance. There's no other TCP running, so it's pretty clear to read.

Posting this a issue because I am not sure if this is actually expected. Feel free to move it to a discussion if it's not at the right place here.