k8s.io: test.py isn't exercised during presubmit

[spiffxp]

This allows people such as myself (who definitely like seeing tests pass, but rely on CI to run all the things) to merge PR's that pass presubmits, but will fail to deploy.

e.g. #2334 went through multiple eyes for review, everyone thought it looked great... and then I needed to followup with #2347

I'm not sure if the solution is to standup a local nginx, pull the redirect spec out such that there's less copy-paste between the config and the tests, or something else.

/wg k8s-infra
/sig contributor-experience
/kind bug
/priority important-longterm

[rajibmitra]

hi @spiffxp I would like to work on this.

[BenTheElder]

please do! :-)
you don't have to ask to work on something.

[MadhavJivrajani]

/assign @rajibmitra

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[BenTheElder]

/lifecycle frozen