kubernetes-security fork CI

[cblecker]

The kubernetes-security fork currently doesn't have functioning CI. There is a lack of clarity around ownership/priority/resourcing of it.

We should work with the PSC, test-infra team, and wg-k8s-infra to develop a game plan with ownership/staffing to properly maintain private test infrastructure for the security fork.

cc: @kubernetes/product-security-committee

[cblecker]

There are some technical details in this private issue https://github.com/kubernetes-security/kubernetes/issues/37

[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

[justaugustus]

This is probably still active.
/remove-lifecycle stale
/lifecycle frozen
/priority critical-urgent

[nikhita]

Changing priority to important-longterm... please bump the priority again if needed!

/remote-priority critical-urgent
/priority important-longterm

[nikhita]

/remove-priority critical-urgent

[justaugustus]

Can we move this one to k/org or k/security?
/committee product-security
/sig release testing
/area release-eng

[k8s-ci-robot]

@justaugustus: The label(s) area/release-eng cannot be applied, because the repository doesn't have them

In response to this:

Can we move this one to k/org or k/security?
/committee product-security
/sig release testing
/area release-eng

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.

[nikhita]

Confirmed with @joelsmith that PSC would own this long term. Moving to k/security.

[joelsmith]

Just spoke to @nikhita on slack about this. She's going to create a corresponding issue in the PSC's repo so this can be closed. We'll track it or find someone to track it. Thanks!

[joelsmith]

What?!? You can move an issue to another repo? My mind is blown!

[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