Serving: Need an E2E test for the case when HTTPS server is enabled and HTTP server is disabled

[ZhiminXiang]

In what area(s)?

/area networking
/area test-and-release

Describe the feature

Currently we don't have an E2E test for the case where the HTTPS server of Gateway is configured while HTTP server of Gateway is disabled or configured to redirect HTTP traffic to HTTPS.

We got several related issues for this use case:
https://github.com/knative/serving/issues/5129
https://github.com/knative/serving/issues/4897

In the test, the TLS certificate used by Gateway does not need to be CA signed. It could be self-signed.

[JRBANCEL]

Should we run all the tests with different settings?

• HTTP
• HTTP & HTTPS
• No HTTP & HTTPS

It would be the same tests, but config-network would be different.
In a different test leg.

[ZhiminXiang]

@JRBANCEL Good point. I think we should do that.

[taragu]

I'm interested. Can I work on this issue?

[ZhiminXiang]

Sure. thanks for picking it up. @taragu

[JRBANCEL]

Yes, as I said in my previous comment, ideally we would like to be able to run the same E2E tests with different settings (HTTP, no HTTP, etc...), the same way we have different E2E legs today (pull-knative-serving-istio-1.1-mesh, pull-knative-serving-istio-1.1-no-mesh, etc...).
And it would be awesome to have those legs show up in https://testgrid.knative.dev/serving.

[knative-housekeeping-robot]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

[taragu]

/remove-lifecycle stale

[knative-housekeeping-robot]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

[knative-housekeeping-robot]

Stale issues rot after 30 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.
Rotten issues close after an additional 30 days of inactivity.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle rotten

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.