Knative serving with contour network broken the default httpproxy behavior

[simsnow]

What version of Knative?

0.16.0
network: contour

Expected Behavior

the contour crd httpproxy object work work fine

Actual Behavior

httpproxy can not work

Steps to Reproduce the Problem

1. install knative serving with contour

apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
spec:
  ingress:
    contour:
      enabled: true
  config:
    domain:
      xxxx.com: ""
    network:
      ingress-class: "contour.ingress.networking.knative.dev"

2. create 2 ksvc

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: contour-test-android
spec:
  template:
    spec:
      containers:
        - image: ghcr.io/knative/helloworld-go:latest
          env:
            - name: TARGET
              value: "contour test android"
---
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: contour-test-ios
spec:
  template:
    spec:
      containers:
        - image: ghcr.io/knative/helloworld-go:latest
          env:
            - name: TARGET
              value: "contour test ios"

3. create a httpproxy route to the above ksvc

apiVersion: projectcontour.io/v1
kind: HTTPProxy
metadata:
  name: contour-test
spec:
  ingressClassName: contour
  virtualhost:
    fqdn: contour-test.default.xxxx.com
  routes:
    - conditions:
      - header:
          name: x-os
          contains: ios
      services:
        - name: contour-test-ios
          port: 80
    - conditions:
      - header:
          name: x-os
          contains: android
      services:
        - name: contour-test-android
          port: 80

4. check the httpproxy status

kubectl describe httpproxies.projectcontour.io contour-test
...
Status:
  Current Status:  NotReconciled
  Description:     Waiting for controller
...

Thought

the contour installed by knative change the default behavior? only watch ksvc?

[skonto]

cc @dprotaso