Edit: this bug originally covered only the status of a waypoint not being updated, but on further investigation, it was discovered that this impacts all gateways, and causes them to be improperly programmed, not just to lack status.

Is this the right place to submit this?

• This is not a security vulnerability or a crashing bug

  This is not a question about how to use Istio
  To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.

Bug Description

When using a gateway with an istio.io/rev label pointing to a tag rather than a revision, the gateway is ignored during the construction of the pushContext, causing incorrect XDS to be delivered to it, as well as preventing the status field from being set (if present). This issue affects both Istio Gateways and K8s Gateways across all methods of orchestration (helm, injection, managed, unmanaged).

Version

This issue was discovered on 1.24.1, but appears to have been present since tags were added to the codebase, sometime before 1.16.

client version: 1.24.1
control plane version: 1.24.1
data plane version: 1.24.1 (7 proxies)

Additional Information

to reproduce:

istioctl install --set profile=ambient --revision 1-24-1
istioctl tag set rapid --revision 1-24-1
istioctl waypoint apply --revision rapid --for all

Notice that status is not updated on the waypoint gateway resource. Additionally, run istioctl pc -o json against the gateway pod, and store this as tagged.json. Finally, run kubectl label deployment waypoint istio.io/rev=1-24-1 --overwrite to use the explicit revision rather than the tag. Status should now be set, and the above pc command should have several thousand lines of significant difference frmo tagged.json.