Test-infra: Split prow config from prow codebase

[stevekuznetsov]

We're getting close to being ready for the move. Items we know we need to accomplish is here:

• [x] reconfigure config updater for prow.k8s.io https://github.com/kubernetes/test-infra/pull/11781
• [x] move remaining config files to config/ and run the config-bootstrapper in case any changed had landed in between https://github.com/kubernetes/test-infra/pull/11784
• [x] ensure all references to original config locations are updated
• [x] move prow/cluster to config/cluster
• [x] ensure all auto-bump etc automation around prow/cluster is updated
• [ ] submit KEP to create repo

/cc @spiffxp @fejta @cjwagner @BenTheElder @krzyzacy

[stevekuznetsov]

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[StevenACoffman]

/remove-lifecycle stale

[spiffxp]

Need to see what PR's modify config.yaml and plugin.yaml and decide if we want those to go through rebase fun

[spiffxp]

/milestone v1.16
/assign

[spiffxp]

/assign @cjwagner

[spiffxp]

Rescoping based on what we thought was feasible for this quarter, moving to its own repo can be done as a followup

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[stevekuznetsov]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

/remove-lifecycle stale

move prow/cluster to config/cluster
ensure all auto-bump etc automation around prow/cluster is updated

sounds relatively easy, maybe we should do that. @cjwagner @fejta thoughts?

submit KEP to create repo

you actually just have to file an issue in k/org after getting consensus from the SIG on wanting it, no KEP necessary. the process is pretty lightweight. moving code is a little more involved to do cleanly.

[fejta]

Moving prow/cluster files into config/prow or somewhat like that sgtm

[spiffxp]

/area prow

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

/remove-lifecycle stale

I think this is _mostly_ done? pretty much everything is under config/.

submit KEP to create repo

we can actually do this with much less than a KEP, SIGs can sponsor a repo without going full KEP 🙃

[BenTheElder]

I don't think there's any config lingering under prow/ now. some scripts / makefile stuff.

[alvaroaleman]

Yeah, the config is pretty much moved out of the prow directory. What would be needed to move prow into its own repo is:

• The repo itself
• Exporting the code to the new repo
• Setting up all prow-related jobs onto the new repo
• Announcing this in case other projects reference prow code (kubetest2?)
• Updating all references outside of /prow to prow

The point that is presumably most of the work is setting up the jobs on the new repo. It would be great to make this happen though, to better separate concerns and make certain tasks like updating dependencies easier :upside_down_face:

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[StevenACoffman]

/remove-lifecycle rotten