kubernetes
REQUEST: Migrate cncf-infra/verify-conformance
New repo, staging repo, or migrate existing
verify-conformance
Is it a staging repo?
yes
Requested name for new repository
verify-conformance
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
hh, heyste, cooldracula, BobyMCbobs
Who should have write access?
hh, heyste, cooldracula, BobyMCbobs
Who should be listed as approvers in OWNERS?
hh, heyste, cooldracula, BobyMCbobs
Who should be listed in SECURITY_CONTACTS?
hh, heyste, cooldracula, BobyMCbobs
What should the repo description be?
CNCF CI bot for verifying Kubernetes conformance product submissions
What SIG and subproject does this fall under?
sig-architecture
Please provide references to appropriate approval for this new repo
- https://kubernetes.slack.com/archives/C78F00H99/p1683662771165129
- https://kubernetes.slack.com/archives/C78F00H99/p1683663250267499
- https://groups.google.com/u/3/g/kubernetes-sig-architecture/c/bEx9fppYQ0Q/m/8ZyumVYUBwAJ
Additional context for request
CNCF is wanting to donate Kubernetes conformance infrastructure (cncf/apisnoop, cncf-infra/verify-conformance, conformance-gate) to sig-architecture and sig-k8s-infra.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Migrating the GitHub App (https://github.com/organizations/cncf-infra/settings/apps/prow-cncf-io) is also a required part of this task.
The problem isn't kubernetes/owners, we need the SIG TLs to accept/deny. Will ping SIG Arch again.
Edit: We do have a +1 from dims in the mailinglist thread but usually we'd see input from the other leads before considering a repo accepted or not. Once it's clearly accepted then we're onto kubernetes/owners to do the mechanical bits.
This is approved, we also have Derek's +1 in the mailinglist thread.
So now it's over to @kubernetes/owners 🙏
Okay, once the 2 open PRs are merged things should be good to go. There is one follow up item - iiamabby was not a member of k-sigs and that can be handled later + adding to the team.
@mrbobbytables: Closing this issue.
In response to this:
we are good! going to go ahead and close this out :) /close
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-sigs/prow repository.
