• Summary: Removing tags from a Knative Service traffic block does not delete the corresponding HTTPRoute; stale routes remain after reconciliation.
• Expected: Owned HTTPRoutes no longer referenced by current traffic tags are pruned on reconciliation.
• Actual: Tag-specific HTTPRoutes (e.g., okay-....) remain until manually deleted.

Steps to Reproduce:

1. Create a Knative Service with traffic entries that include tagged routes (e.g., tag: okay, tag: canary).
2. Wait for reconciliation; tag-specific HTTPRoutes are created.
3. Edit the Service to remove one or more tags from the traffic spec (revisions unchanged).
4. Observe after reconciliation that the corresponding tag HTTPRoutes are not deleted.

Impact:

• Stale routing config persists (unexpected hosts/routes remain) until manual deletion.

Workaround:

• Manually delete the stale HTTPRoutes.