Aaron Crickenberger
Aaron Crickenberger
Prompted by https://github.com/kubernetes/kubernetes/pull/94367 getting cherry picked with no explicit documentation as to why From [this slack thread](https://kubernetes.slack.com/archives/CJH2GBF7Y/p1599751989067900) with @justaugustus > We commonly backport deps in the same minor stream >...
The dream: updating sigs.yaml would result in automatic create/deletion of resources managed by other tooling, e.g. - GitHub labels - tool: label_sync - repo: kubernetes/test-infra - GitHub teams (peribolos) -...
ref: https://github.com/kubernetes/community/blob/master/contributors/devel/conformance-tests.md#sample-conformance-test I would like all of the existing conformance tests to have consistent formatting, and descriptions. Someone should be able to read this doc and feel like all behaviors...
My read of current pod-utils code is that it assumes `base_ref` to always be present / non-empty (ref: https://github.com/kubernetes/test-infra/pull/20665#issuecomment-769961333) It looks like there are 435 jobs that explicitly reference `master`,...
**What should be cleaned up or changed**: There are sundry files within prow that can probably use more specific terms, or the generic terms "allowlist/denylist" ``` $ ag -l whitelist\|blacklist...
### Describe the issue We've reached lazy consensus on some chair and tech lead additions - Add @michelle192837 as chair ([mailing list thread](https://groups.google.com/g/kubernetes-sig-testing/c/1p4_YnsKhsk)) - Add @aojea and @pohly as tech...
Related: - Part of: https://github.com/kubernetes/community/issues/6913
**What happened**: Context: https://github.com/kubernetes/k8s.io/issues/1576#issuecomment-767691409 As the volume of image-pushing jobs running on the prow build cluster in k8s-infra-prow-build-trusted has grown, we're starting to bump into a GCB service quota (GetRequestsPerMinutePerProject)...
**What type of PR is this?** /kind cleanup **What this PR does / why we need it**: WIP because: - using this to exercise CI This brings kubetest2 back up...
Peribolos supports defining which repos a given team should have which level of access to (ref: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos#org-configuration) Currently this is all done manually. I think it would reduce our toil...