kubernetes-security fork CI
cblecker opened this issue · comments
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
There are some technical details in this private issue https://github.com/kubernetes-security/kubernetes/issues/37
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
This is probably still active.
/remove-lifecycle stale
/lifecycle frozen
/priority critical-urgent
Changing priority to important-longterm... please bump the priority again if needed!
/remote-priority critical-urgent
/priority important-longterm
/remove-priority critical-urgent
Can we move this one to k/org or k/security?
/committee product-security
/sig release testing
/area release-eng
@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.
Confirmed with @joelsmith that PSC would own this long term. Moving to k/security.
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!
What?!? You can move an issue to another repo? My mind is blown!
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
Is this: /sig security ?
Is this: /sig security ?
Yep, either SIG Security or PSC.
@IanColdwater @tabbysable adding the SIG Security label so that this is not lost, please change if needed! :)
/remove-lifecycle stale
/sig security
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
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
/lifecycle frozen