Summary
When I expose a TenantControlPlane with Gateway API, Kamaji shows the wrong address in status.
$ k get tcp k8s-133 demo-tcp-1
NAME VERSION INSTALLED VERSION STATUS CONTROL-PLANE ENDPOINT KUBECONFIG DATASTORE AGE
k8s-133 v1.33.0 v1.33.0 Ready 172.19.255.100:6443 k8s-133-admin-kubeconfig default 19m
demo-tcp-1 v1.32.0 v1.32.0 Ready 10.96.58.78:6443 demo-tcp-1-admin-kubeconfig default 8m33s
It shows the internal Service IP, but it should show the Gateway hostname e.g. c11.cluster.dev:6443.
Expected behavior
When .spec.controlPlane.gateway is used, Kamaji should show the Gateway hostname/address instead:
Actual behavior
Kamaji shows the Service ClusterIP instead of the Gateway hostname.
Summary
When I expose a
TenantControlPlanewith Gateway API, Kamaji shows the wrong address in status.It shows the internal Service IP, but it should show the Gateway hostname e.g.
c11.cluster.dev:6443.Expected behavior
When
.spec.controlPlane.gatewayis used, Kamaji should show the Gateway hostname/address instead:Actual behavior
Kamaji shows the Service ClusterIP instead of the Gateway hostname.