Add CI for images/kube-webhook-certgen

[invidian]

What this PR does / why we need it:

As a follow up to PR #7641, this commit adds some basic e2e tests for
kube-webhook-certgen image.

Signed-off-by: Mateusz Gozdek mgozdek@microsoft.com

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

How Has This Been Tested?

Locally.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

@invidian: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a 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.

[k8s-ci-robot]

Hi @invidian. 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.

[rikatz]

/ok-to-test

[rikatz]

nit here: test-image-what? Would be good to explain we are testing image-webhook.

Approving and lgtming here anyway, I will put a hold if you think this deserves to be fixed, otherwise just remove the hold !

Thanks

[invidian]

Hm, the section above is named test-image-build, maybe this should be named image-test then? To indicate that we run tests for images?

I assume test-image-build was previously used only for building test image and then evolved into building other images as well, without being renamed?

[rikatz]

/lgtm
/approve
/hold
Thanks

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: invidian, rikatz

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:

• OWNERS [rikatz]

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

[invidian]

@rikatz BTW, when could we expect next release of k8s.gcr.io/ingress-nginx/kube-webhook-certgen? Including #7641 :)

[rikatz]

@invidian we can release the new one split from the rest of the process :)

Is just a matter of merging and promoting the image.

Ping me on slack, can show you how to do that!
/hold cancel