Bump Knative serving internal TLS CI to 4.11

[nak3]

This patch bumps Knative Serving internal TLS CI to 4.11.

It failed for some reason so still uses on 4.10. Please also refer to #31756 (comment)

[nak3]

knative-serving repo test passed openshift/knative-serving#1227 but this repo does not - log.

I guess the name 411-tls exceeds some name limitation.

[nak3]

#32080 (comment) is an old name's result. It should be ignored.

[nak3]

/cc @skonto @mgencur

[mgencur]

There's already a file called openshift-knative-serving-release-next__411.yaml which calls the make target test-e2e. And now you're adding a file called openshift-knative-serving-release-next__tls.yaml which has two prow checks and then call both make test-e2e and make test-e2e-tls. So there's duplication. The CI will run the same target twice (make test-e2e).
Aside from that the two prow checks from this new file are called tls-e2e-aws-ocp-tls-411 and tls-e2e-aws-ocp-411 even though just one of them runs tls.
You should probably delete the file openshift-knative-serving-release-next__tls.yaml completely and move the prow check for tls to openshift-knative-serving-release-next__411.yaml.

[mgencur]

Need to run make jobs again.

[mgencur]

/lgtm
/hold
Hold for tests.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mgencur, nak3

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/knative-serving/OWNERS [mgencur,nak3]
• ci-operator/jobs/openshift/knative-serving/OWNERS [mgencur,nak3]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[skonto]

Is this run elsewhere? I guess we remove 4.10 completely in favor of 4.11.

[mgencur]

So far, we had:

openshift-knative-serving-release-next__410-tls.yaml
openshift-knative-serving-release-next__411.yaml
openshift-knative-serving-release-next__46.yaml
openshift-knative-serving-release-next__47.yaml

IMO, it would be fine to have just 4.8 and 4.11. It depends what you want. Please also see my comment here: openshift/knative-serving#1239 (comment)

[skonto]

I like the idea of running against the oldest and the newest version more because release-next is supposed to introduce new stuff and for sure we want to test compatibility to know ahead in time if something fails.
So I agree with the comment we can update later for 1.26 anyway.

[nak3]

/hold cancel

It passed https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/32080/rehearse-32080-pull-ci-openshift-knative-serving-release-next-411-e2e-aws-ocp-tls-411/1567768330087960576

[openshift-ci]

@nak3: Updated the following 2 configmaps:

• ci-operator-misc-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-knative-serving-release-next__410-tls.yaml using file ``
  • key openshift-knative-serving-release-next__411.yaml using file ci-operator/config/openshift/knative-serving/openshift-knative-serving-release-next__411.yaml
• job-config-misc configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-knative-serving-release-next-postsubmits.yaml using file ci-operator/jobs/openshift/knative-serving/openshift-knative-serving-release-next-postsubmits.yaml
  • key openshift-knative-serving-release-next-presubmits.yaml using file ci-operator/jobs/openshift/knative-serving/openshift-knative-serving-release-next-presubmits.yaml

Details

In response to this:

This patch bumps Knative Serving internal TLS CI to 4.11.

It failed for some reason so still uses on 4.10. Please also refer to #31756 (comment)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@nak3: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/openshift/knative-serving/release-next/tls-e2e-aws-ocp-tls-411	d301f01	link	unknown	/test pj-rehearse
ci/rehearse/openshift/knative-serving/release-next/411-tls-e2e-aws-ocp-411-continuous	5f6b32f	link	unknown	/test pj-rehearse

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.