gateway status programmed should not be set until the proxy has been programmed

[eitansuez]

Gloo Edge Product

Open Source

Gloo Edge Version

1.18.7

Kubernetes Version

1.31.4

Describe the bug

while playing with gloo gateway (open source), i'm noticing something odd about the status of a provisioned gateway.

specifically, i saw this sequence of events:

1. create a gateway:

   $ kubectl apply -f http/gtw.yaml
   gateway.gateway.networking.k8s.io/my-gateway created

2. wait for the gateway to be programmed:

   $ kubectl wait --for=condition=Programmed=True gtw/my-gateway
   gateway.gateway.networking.k8s.io/my-gateway condition met

3. check the pod..

   $ k get pod
   NAME                                     READY   STATUS              RESTARTS   AGE
   gloo-proxy-my-gateway-5bcddf75d9-p6l88   0/1     ContainerCreating   0          5s

how can the pod be in ContainerCreating state if the status says gateway is programmed?
i expect the controller to set the status to programmed only after the proxy has been programmed.

context, from lawrence:

we basically treat it as programmed successfully when we have translated the correct resources and put them in the xds cache (i.e. to the control plane it’s programmed) but it doesn’t actively consider the state of the proxy deployment itself
so this is a legitimate gap, although where it’s a bug/feature I can see a bit more debate

Expected Behavior

i expect the controller to set the status to programmed only after the proxy has been programmed.

Steps to reproduce the bug

see above description

Additional Environment Detail

No response

Additional Context

No response