featuretests: TestIngressClassUpdate passes but shouldn't

[youngnick]

The featuretest TestIngressClassUpdate creates an object with a given ingress class, checks that it is processed correctly, then updates that object so it does not have the same ingress class, and checks that its status has been cleared.

Because of changes to the way we send status updates, this test does not reflect what Contour actually does; currently, Contour will leave the status of objects that fall out of scope alone and not clear them.

When updating featuretests for #2495, this test is breaks and is not easily fixable. I've marked it to skip for now, this is a tracking issue to come back and fix this.

Currently, the test checks for the status being blank, if we want this test to pass, we're going to have to actually do that and send the update to the apiserver. Currently, we don't support clearing status.

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

• Mark this Issue as fresh by commenting
• Close this Issue
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

• Mark this Issue as fresh by commenting
• Close this Issue
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack