Configure post-submit test for HNC

[GinnyJI]

Note: this changed has not been tested, I don't know how to test it. If
this change break then post-submit tests for HNC will simply not run,
but developers can still merge in their changes because it's not
supposed to affect pre-submit tests.

Here's what I referenced for this change:

test-infra/config/jobs/kubernetes/sig-network/ingress-nginx.yaml

Lines 166 to 195 in 9b4e473

	- name: pull-ingress-nginx-e2e-1-15
	always_run: false
	decorate: true
	decoration_config:
	timeout: 1h
	max_concurrency: 5
	path_alias: k8s.io/ingress-nginx
	#run_if_changed: '\.go$|^rootfs/'
	labels:
	preset-kind-volume-mounts: "true"
	preset-dind-enabled: "true"
	spec:
	containers:
	- image: gcr.io/k8s-testimages/krte:v20200824-5d057db-master
	command:
	- wrapper.sh
	- bash
	- -c
	- curl -sSL https://kind.sigs.k8s.io/dl/latest/linux-amd64.tgz | tar xvfz - -C "${PATH%%:*}/" && make kind-e2e-test
	# docker-in-docker needs privileged mode
	securityContext:
	privileged: true
	env:
	- name: REPO_INFO
	value: https://github.com/kubernetes/ingress-nginx
	- name: K8S_VERSION
	value: v1.15.11@sha256:6cc31f3533deb138792db2c7d1ffc36f7456a06f1db5556ad3b6927641016f50
	annotations:
	testgrid-dashboards: sig-network-ingress-nginx
	testgrid-tab-name: e2e-1-15

[k8s-ci-robot]

Hi @GinnyJI. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[GinnyJI]

/assign @BenTheElder
/cc @adrianludwin

[k8s-ci-robot]

@GinnyJI: GitHub didn't allow me to request PR reviews from the following users: adrianludwin.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/assign @BenTheElder
/cc @adrianludwin

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.

[adrianludwin]

This all lgtm but I don't know the technical details at all. But it does seem to express how we in wg-multitenancy want this to run!

[adrianludwin]

Ben's not going to be able to have a look. Tasha, Sanjeev, Ryan - it looks like you have the ability to approve in this directory?

/assign @tashimi
/assign @srampal

[k8s-ci-robot]

@adrianludwin: GitHub didn't allow me to assign the following users: rjbez217.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Ben's not going to be able to have a look. Tasha, Sanjeev, Ryan - it looks like you have the ability to approve in this directory?

/assign @tashimi
/assign @rjbez217
/assign @srampal

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.

[adrianludwin]

/assign @rjbez17

[rjbez17]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GinnyJI, rjbez17

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes-sigs/wg-multi-tenancy/OWNERS [rjbez17]

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

[rjbez17]

/ok-to-test

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[adrianludwin]

lgtm, let's wait until the script has been submitted in our repo and then Ryan or Tasha can approve this.

[spiffxp]

/test pull-test-infra-integration
#20498 (comment)

[adrianludwin]

Ginny and I just started working on this again last week - hopefully we'll have something to submit ~soon.

[adrianludwin]

Ok, we've submitted and tested the new script locally (kubernetes-retired/multi-tenancy#1369). I suspect I'll want to create a new PR based off of this one instead of trying to reuse it; I'll close this PR if I do.

[rjbez17]

@adrianludwin @GinnyJI now that we kubernetes-retired/multi-tenancy#1369 merged, are we ready to come back to this? Did you want to create a new PR or keep this one?

[adrianludwin]

I think I'll create a new PR. I'll get to it later this week (Friday is usually my HNC coding day these days!)

…

On Wed, Feb 3, 2021 at 10:31 AM Ryan Bezdicek ***@***.***> wrote: @adrianludwin <https://github.com/adrianludwin> @GinnyJI <https://github.com/GinnyJI> now that we kubernetes-retired/multi-tenancy#1369 <kubernetes-retired/multi-tenancy#1369> merged, are we ready to come back to this? Did you want to create a new PR or keep this one? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#19856 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE43PZFYPYNWOVMXZBUZGELS5FT6ZANCNFSM4TLPCYWQ> .

[adrianludwin]

/close

Replaced by #20773

[k8s-ci-robot]

@adrianludwin: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

Replaced by #20773

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.

[adrianludwin]

@GinnyJI can you please close this issue?

[GinnyJI]

/close

[k8s-ci-robot]

@GinnyJI: Closed this PR.

In response to this:

/close

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.