-
Notifications
You must be signed in to change notification settings - Fork 2.6k
/
plugins.yaml
1899 lines (1743 loc) · 52.4 KB
/
plugins.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# Plugin configuration
---
triggers:
- repos:
- kubernetes-sigs/cluster-api
- kubernetes-sigs/cluster-api-provider-azure
- kubernetes-sigs/cluster-api-provider-vsphere
- kubernetes-sigs/cloud-provider-azure
join_org_url: "https://git.k8s.io/community/community-membership.md#member"
only_org_members: true
trigger_github_workflows: true
- repos:
- kubernetes
- kubernetes-client
- kubernetes-csi
- kubernetes-sigs
join_org_url: "https://git.k8s.io/community/community-membership.md#member"
only_org_members: true
- repos:
- google/cadvisor
- GoogleCloudPlatform/k8s-multicluster-ingress
join_org_url: "https://git.k8s.io/community/community-membership.md#member"
- repos:
- containerd/cri
join_org_url: "https://github.com/containerd/project/blob/main/MAINTAINERS"
- repos:
- containerd/containerd
join_org_url: "https://github.com/containerd/project/blob/main/MAINTAINERS"
trigger_github_workflows: true
- repos:
- etcd-io
join_org_url: "https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md"
trigger_github_workflows: true
- repos:
- bazelbuild
- repos:
- kubernetes/utils
join_org_url: "https://git.k8s.io/community/community-membership.md#member"
trigger_github_workflows: true
owners:
mdyamlrepos:
- kubernetes/website
skip_collaborators:
- kubernetes-sigs/contributor-playground
approve:
- repos:
- kubernetes/cluster-registry
- kubernetes/contrib
- kubernetes/dashboard
- kubernetes/dns
- kubernetes/examples
- kubernetes/federation
- kubernetes/gengo
- kubernetes/ingress-gce
- kubernetes/ingress-nginx
- kubernetes/klog
- kubernetes/kubeadm
- kubernetes/kubectl
- kubernetes/kubernetes-template-project
- kubernetes/kube-state-metrics
- kubernetes/minikube
- kubernetes/node-problem-detector
- kubernetes/perf-tests
- kubernetes/steering
- kubernetes/system-validators
- kubernetes/utils
require_self_approval: false
lgtm_acts_as_approve: true
- repos:
- kubernetes/cloud-provider-aws
- kubernetes/kops
- kubernetes/website
- kubernetes-sigs/external-dns
require_self_approval: true
lgtm_acts_as_approve: false
- repos:
- kubernetes/enhancements
- kubernetes/kubernetes
- kubernetes-client
- kubernetes-csi
- kubernetes-sigs
require_self_approval: false
- repos:
- kubernetes/cloud-provider-openstack
- kubernetes-sigs/cluster-api
- kubernetes-sigs/cluster-api-operator
- kubernetes-sigs/cluster-api-provider-aws
- kubernetes-sigs/cluster-api-provider-azure
- kubernetes-sigs/cluster-api-provider-vsphere
- kubernetes-sigs/descheduler
- kubernetes-sigs/image-builder
require_self_approval: true
ignore_review_state: true
- repos:
- bazelbuild
- kubernetes-sigs/bom
- kubernetes-sigs/boskos
- kubernetes-sigs/cluster-api-provider-digitalocean
- kubernetes-sigs/cluster-api-provider-gcp
- kubernetes-sigs/cri-tools
- kubernetes-sigs/downloadkubernetes
- kubernetes-sigs/e2e-framework
- kubernetes-sigs/promo-tools
- kubernetes-sigs/k8s-gsm-tools
- kubernetes-sigs/kind
- kubernetes-sigs/kubetest2
- kubernetes-sigs/mdtoc
- kubernetes-sigs/prow
- kubernetes-sigs/release-notes
- kubernetes-sigs/release-sdk
- kubernetes-sigs/release-utils
- kubernetes-sigs/security-profiles-operator
- kubernetes-sigs/slack-infra
- kubernetes-sigs/tejolote
- kubernetes-sigs/testgrid-json-exporter
- kubernetes-sigs/zeitgeist
- kubernetes/community
- kubernetes/k8s.io
- kubernetes/org
- kubernetes/publishing-bot
- kubernetes/release
- kubernetes/repo-infra
- kubernetes/sig-release
- kubernetes/test-infra
- kubernetes/cloud-provider-gcp
require_self_approval: false
ignore_review_state: false
- repos:
- kubernetes-sigs/gateway-api
lgtm_acts_as_approve: false
- repos:
- kubernetes-sigs/aws-ebs-csi-driver
require_self_approval: true
lgtm_acts_as_approve: false
ignore_review_state: true
help:
help_guidelines_summary: |
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
# Lower bounds in number of lines changed; XS is assumed to be zero.
size:
s: 10
m: 30
l: 100
xl: 500
xxl: 1000
label:
additional_labels:
# This label is used by the API review process
# https://git.k8s.io/community/sig-architecture/api-review-process.md#mechanics
- api-review
# These labels are used to make Tide merge with a non-default merge method
- tide/merge-method-merge
- tide/merge-method-rebase
- tide/merge-method-squash
# This label, for k/website, identifies issues relevant to https://katacoda.com/
- team/katacoda
# This label, for k/website, identifies PRs with large refactoring changes
- refactor
restricted_labels:
kubernetes/kubernetes:
# Security Response Committee (SRC) is allowed to add this label,
# to new and existing GitHub Issues and PRs that announce a fixed CVE triaged by SRC
- allowed_teams:
- security-response-committee
# SIG Security Tooling Lead is an allowed user to assist SRC in this CVE feed automation
allowed_users:
- pushkarj
# This label is used to filter/tag CVEs announced by SRC
label: official-cve-feed
kubernetes/enhancements:
# Restrict setting of tracked/* labels to the enhancements team.
- label: tracked/no
allowed_teams:
- release-team-enhancements
- release-team-leads
- label: tracked/yes
allowed_teams:
- release-team-enhancements
- release-team-leads
- label: tracked/out-of-tree
allowed_teams:
- release-team-enhancements
- release-team-leads
# Restrict setting of 'lead-opted-in' label to SIG leads.
- label: lead-opted-in
allowed_teams:
- release-team-enhancements
- release-team-leads
- sig-api-machinery-leads
- sig-apps-leads
- sig-architecture-leads
- sig-auth-leads
- sig-autoscaling-leads
- sig-cli-leads
- sig-cloud-provider-leads
- sig-cluster-lifecycle-leads
- sig-contributor-experience-leads
- sig-docs-leads
- sig-instrumentation-leads
- sig-k8s-infra-leads
- sig-multicluster-leads
- sig-network-leads
- sig-node-leads
- sig-release-leads
- sig-scalability-leads
- sig-scheduling-leads
- sig-security-leads
- sig-storage-leads
- sig-testing-leads
- sig-windows-leads
lgtm:
- repos:
- bazelbuild
- kubernetes-sigs/aws-ebs-csi-driver
- kubernetes-sigs/bom
- kubernetes-sigs/boskos
- kubernetes-sigs/controller-runtime
- kubernetes-sigs/cluster-api-provider-digitalocean
- kubernetes-sigs/cluster-api-provider-gcp
- kubernetes-sigs/cri-tools
- kubernetes-sigs/downloadkubernetes
- kubernetes-sigs/e2e-framework
- kubernetes-sigs/etcdadm
- kubernetes-sigs/external-dns
- kubernetes-sigs/promo-tools
- kubernetes-sigs/k8s-gsm-tools
- kubernetes-sigs/kind
- kubernetes-sigs/kubetest2
- kubernetes-sigs/mdtoc
- kubernetes-sigs/prow
- kubernetes-sigs/release-notes
- kubernetes-sigs/release-sdk
- kubernetes-sigs/release-utils
- kubernetes-sigs/security-profiles-operator
- kubernetes-sigs/tejolote
- kubernetes-sigs/zeitgeist
- kubernetes/cloud-provider-aws
- kubernetes/k8s.io
- kubernetes/kops
- kubernetes/release
- kubernetes/repo-infra
- kubernetes/sig-release
- kubernetes/test-infra
review_acts_as_lgtm: true
- repos:
- kubernetes/kubernetes
- kubernetes/website
- kubernetes-sigs/node-feature-discovery
- kubernetes-sigs/cluster-api
- kubernetes-sigs/cluster-api-operator
- kubernetes-sigs/cluster-api-provider-azure
- kubernetes-sigs/cluster-api-provider-vsphere
- kubernetes-sigs/kueue
store_tree_hash: true
blockades:
- repos:
- kubernetes/kubernetes
blockregexps:
- ^examples/
explanation: "examples/ has moved to https://github.com/kubernetes/examples/"
- repos:
- kubernetes/kubernetes
blockregexps:
- ^pkg/util/[^/]+\.go$
explanation: "Utility code must be added to a subpackage like pkg/util/flag, not pkg/util directly. See: #49923"
- repos:
- kubernetes/kubernetes
blockregexps:
- ^test/conformance/testdata/conformance.yaml$
branchregexp: "^release-*"
explanation: "`test/conformance/testdata/conformance.yaml` cannot be updated on release branches."
- repos:
- kubernetes/community
blockregexps:
- ^events/2016
- ^events/2017
- ^events/2018
- ^events/elections/2017
- ^events/elections/2018
- ^events/elections/2019
explanation: "These files are historical, and from events that have already occurred."
- repos:
- kubernetes/community
blockregexps:
- ^keps/
explanation: "KEPs have been relocated to [kubernetes/enhancements](https://git.k8s.io/enhancements/)! Please submit any updates there."
- repos:
- kubernetes/community
blockregexps:
- ^contributors/design-proposals/
explanation: "The Design Proposal process has been deprecated in favor of [Kubernetes Enhancement Proposals (KEP)](https://git.k8s.io/enhancements/). These documents are here for historical purposes only."
- repos:
- kubernetes/enhancements
blockregexps:
- ^keps/NEXT_KEP_NUMBER$
explanation: "KEP numbers are obsolete. Please remove any changes to `NEXT_KEP_NUMBER` from this PR and ensure the KEP filename is the draft date and KEP title e.g., `YYYYMMDD-pony-controller.md`"
- repos:
- kubernetes/release
blockregexps:
- ^push-build.sh
explanation: "Changes to push-build.sh will immediately affect the Kubernetes CI. This PR must be explicitly approved by SIG Release repo admins."
- repos:
- kubernetes/client-go
blockregexps:
- .*
exceptionregexps:
- ^README\.md$
explanation: "We do not accept changes directly against this repository, unless the change is to the `README.md` itself. Please see `CONTRIBUTING.md` for information on where and how to contribute instead."
- repos:
- kubernetes/test-infra
blockregexps:
- ^prow/.+\.md$
exceptionregexps:
- ^prow/(ANNOUNCEMENTS|README)\.md$
explanation: "All Prow documentation (Markdown files) have moved to https://github.com/kubernetes-sigs/prow as part of https://github.com/kubernetes-sigs/prow/issues/4. Instructions for updating existing docs are at https://docs.prow.k8s.io/docs/contribution-guidelines/#updating-existing-docs."
- repos:
- kubernetes/k8s.io
blockregexps:
- ^k8s.gcr.io/
explanation: "k8s.gcr.io Image registry is frozen from April 2023. Please update the manifests in registry.k8s.io folder instead"
blunderbuss:
max_request_count: 2
use_status_availability: true
cat:
key_path: /etc/cat-api/api-key
goose:
key_path: /etc/unsplash-api/honk.txt
heart:
adorees:
- mirandachrist
commentregexp: ".*"
branch_cleaner:
# PreservedBranches is a map of org/repo branches
# format:
# ```
# preserved_branches:
# <org>: ["master", "release"]
# <org/repo>: ["master", "release"]
# ```
# branches in this allow map would be exempt from branch gc
# even if the branches are already merged into the target branch
preserved_branches:
kubernetes-sigs/cloud-provider-azure: ["master", "release-1.1", "release-1.0", "release-1.23", "release-1.24", "release-1.25", "release-1.26", "release-0.7", "release-0.6", "release-0.5", "release-0.1", "kubetest2-aks"]
slack:
mergewarnings:
- repos:
- kubernetes/community
- kubernetes/org
channels:
- sig-contribex
exempt_users:
- k8s-ci-robot
- repos:
- kubernetes/enhancements
channels:
- enhancements
exempt_users:
- k8s-ci-robot
- repos:
- kubernetes/utils
- kubernetes/component-helpers
channels:
- sig-architecture
exempt_users:
- k8s-ci-robot
- k8s-publishing-bot
- repos:
- kubernetes/api
- kubernetes/apiextensions-apiserver
- kubernetes/apimachinery
- kubernetes/apiserver
- kubernetes/client-go
- kubernetes/code-generator
- kubernetes/component-base
- kubernetes/controller-manager
- kubernetes/kube-aggregator
- kubernetes/kube-controller-manager
- kubernetes/sample-apiserver
- kubernetes/sample-controller
channels:
- sig-api-machinery
exempt_users:
- k8s-publishing-bot
- repos:
- kubernetes/pod-security-admission
channels:
- sig-auth
exempt_users:
- k8s-publishing-bot
- repos:
- kubernetes/kms
channels:
- sig-auth-kms-dev
exempt_users:
- k8s-publishing-bot
- repos:
- kubernetes/kubernetes
channels:
- github-management
exempt_users:
- k8s-ci-robot # future home of tide
- k8s-release-robot # anago
exempt_branches:
feature-serverside-apply:
- lavalamp # feature-serverside-apply "branch manager"
- apelisse # feature-serverside-apply "branch manager"
feature-rate-limiting:
- lavalamp # feature-rate-limiting "branch manager"
- deads2k # feature-rate-limiting "branch manager"
- repos:
- kubernetes/test-infra
channels:
- testing-ops
exempt_users:
- k8s-ci-robot
- repos:
- kubernetes/sig-release
- kubernetes/release
channels:
- release-management
exempt_users:
- k8s-ci-robot
- dependabot[bot]
- repos:
- kubernetes/k8s.io
channels:
- sig-k8s-infra
exempt_users:
- k8s-ci-robot
- repos:
- kubernetes/kops
channels:
- kops-dev
exempt_users:
- k8s-ci-robot
- dependabot[bot]
- github-actions[bot]
- repos:
- kubernetes/cluster-api-provider-aws
channels:
- cluster-api-aws
exempt_users:
- k8s-ci-robot
milestone_applier:
kubernetes/enhancements:
master: v1.29
kubernetes/kubernetes:
master: v1.29
release-1.29: v1.29
release-1.28: v1.28
release-1.27: v1.27
release-1.26: v1.26
kubernetes/org:
main: v1.29
kubernetes/release:
master: v1.29
kubernetes/sig-release:
master: v1.29
kubernetes/test-infra:
master: v1.29
kubernetes-sigs/kueue:
main: v0.6
release-0.3: v0.3
release-0.4: v0.4
release-0.5: v0.5
kubernetes/k8s.io:
main: v1.29
kubernetes/kops:
master: v1.29
release-1.28: v1.28
release-1.27: v1.27
release-1.26: v1.26
release-1.25: v1.25
release-1.24: v1.24
release-1.23: v1.23
release-1.22: v1.22
release-1.21: v1.21
release-1.20: v1.20
release-1.19: v1.19
release-1.18: v1.18
release-1.17: v1.17
release-1.16: v1.16
kubernetes-sigs/cluster-api:
main: v1.7
release-1.6: v1.6
release-1.5: v1.5
release-1.4: v1.4
release-1.3: v1.3
release-1.2: v1.2
release-1.1: v1.1
release-1.0: v1.0
release-0.4: v0.4
release-0.3: v0.3
kubernetes-sigs/cluster-api-provider-aws:
main: v1.x
release-1.0: v1.0.x
release-0.7: v0.7.x
release-0.6: v0.6.x
kubernetes-sigs/cluster-api-provider-azure:
main: v1.13
release-1.12: v1.12
release-1.11: v1.11
kubernetes-sigs/cluster-api-provider-digitalocean:
main: v1.1.0
release-1.0: v1.0.0
release-0.5: v0.5.1
kubernetes-sigs/cluster-api-provider-gcp:
main: v1.1.0
release-1.0: v1.0.0
release-0.4: v0.4
release-0.3: v0.3
kubernetes-sigs/cluster-api-provider-vsphere:
main: v1.9
release-1.8: v1.8
release-1.7: v1.7
release-1.6: v1.6
release-1.5: v1.5
release-1.4: v1.4
release-1.3: v1.3
kubernetes-sigs/boskos:
master: v1.23
kubernetes/website:
dev-1.29: 1.29
repo_milestone:
# Default maintainer
'':
# You can curl the following endpoint in order to determine the github ID of your team
# responsible for maintaining the milestones. You may need to specify the page number.
# curl -H "Authorization: token <token>" "https://api.github.com/orgs/<org-name>/teams?page=N"
maintainers_team: milestone-maintainers
maintainers_friendly_name: Milestone Maintainers Team
kubernetes-sigs/controller-runtime:
maintainers_team: controller-runtime-maintainers
maintainers_friendly_name: Controller Runtime Maintainers
kubernetes-sigs/cluster-api:
maintainers_team: cluster-api-maintainers
maintainers_friendly_name: Cluster API Maintainers
kubernetes-sigs/cluster-api-provider-aws:
maintainers_team: cluster-api-provider-aws-maintainers
maintainers_friendly_name: Cluster API Provider AWS Maintainers
kubernetes-sigs/cluster-api-provider-azure:
maintainers_team: cluster-api-provider-azure-maintainers
maintainers_friendly_name: Cluster API Provider Azure Maintainers
kubernetes-sigs/cluster-api-provider-digitalocean:
maintainers_team: cluster-api-provider-digitalocean-maintainers
maintainers_friendly_name: Cluster API Provider DigitalOcean Maintainers
kubernetes-sigs/cluster-api-provider-gcp:
maintainers_team: cluster-api-provider-gcp-maintainers
maintainers_friendly_name: Cluster API Provider GCP Maintainers
kubernetes-sigs/cluster-api-provider-nested:
maintainers_team: cluster-api-provider-nested-maintainers
maintainers_friendly_name: Cluster API Provider Nested Maintainers
kubernetes-sigs/cluster-api-provider-vsphere:
maintainers_team: cluster-api-provider-vsphere-maintainers
maintainers_friendly_name: Cluster API Provider vSphere Maintainers
kubernetes-sigs/node-feature-discovery:
maintainers_team: node-feature-discovery-maintainers
maintainers_friendly_name: Node Feature Discovery Maintainers
kubernetes/community:
maintainers_team: community-milestone-maintainers
maintainers_friendly_name: Community Milestone Maintainers
kubernetes/kops:
maintainers_team: kops-maintainers
maintainers_friendly_name: Kops Maintainers
kubernetes/ingress-nginx:
maintainers_team: ingress-nginx-maintainers
maintainers_friendly_name: Ingress Nginx Maintainers
kubernetes/org:
maintainers_team: owners
maintainers_friendly_name: GitHub Admin Team
kubernetes/website:
maintainers_team: website-milestone-maintainers
maintainers_friendly_name: Website milestone maintainers
kubernetes/kubeadm:
maintainers_team: kubeadm-maintainers
maintainers_friendly_name: Kubeadm maintainers
kubernetes-sigs/kubebuilder:
maintainers_team: kubebuilder-maintainers
maintainers_friendly_name: Kubebuilder Maintainers
kubernetes-sigs/kueue:
maintainers_team: kueue-maintainers
maintainers_friendly_name: Kueue Maintainers
project_config:
project_org_configs:
kubernetes:
org_maintainers_team_id: 3162587 # sig-testing-dummy-project-team
org_default_column_map:
test-infra-dummy-testing-project-plugin:
To do
KEP Implementation Tracking:
To do
project_repo_configs:
kubernetes:
repo_maintainers_team_id: 2460384 # milestone-maintainers
repo_default_column_map:
component-base:
To do
Workloads:
Backlog
website:
repo_maintainers_team_id: 3175912 # website-milestone-maintainers
repo_default_column_map:
component-base:
To do
Doc Writing and Editing:
To do
config_updater:
maps:
label_sync/labels.yaml:
name: label-config
clusters:
test-infra-trusted:
- test-pods
config/prow/config.yaml:
name: config
clusters:
test-infra-trusted:
- default
config/prow/plugins.yaml:
name: plugins
clusters:
test-infra-trusted:
- default
config/jobs/**/*.{yaml,yml}:
name: job-config
gzip: true
clusters:
test-infra-trusted:
- default
experiment/test-configmap.txt:
name: test-configmap
gzip: true
clusters:
test-infra-trusted:
- default
welcome:
- repos:
- kubernetes
- kubernetes-client
- kubernetes-csi
- kubernetes-sigs
message_template: "Welcome @{{.AuthorLogin}}! <br><br>It looks like this is your first PR to <a href='https://github.com/{{.Org}}/{{.Repo}}'>{{.Org}}/{{.Repo}}</a> 🎉. Please refer to our [pull request process documentation](https://git.k8s.io/community/contributors/guide/pull-requests.md) to help your PR have a smooth ride to approval. <br><br>You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. [Here is the bot commands documentation](https://go.k8s.io/bot-commands). <br><br>You can also check if {{.Org}}/{{.Repo}} has [its own contribution guidelines](https://github.com/{{.Org}}/{{.Repo}}/tree/master/CONTRIBUTING.md). <br><br>You may want to refer to our [testing guide](https://git.k8s.io/community/contributors/devel/sig-testing/testing.md) if you run into trouble with your tests not passing. <br><br>If you are having difficulty getting your pull request seen, please follow the [recommended escalation practices](https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#why-is-my-pull-request-not-getting-reviewed). Also, for tips and tricks in the contribution process you may want to read the [Kubernetes contributor cheat sheet](https://git.k8s.io/community/contributors/guide/contributor-cheatsheet/README.md). We want to make sure your contribution gets all the attention it needs! <br><br>Thank you, and welcome to Kubernetes. :smiley:"
require_matching_label:
- missing_label: do-not-merge/needs-kind
org: kubernetes
repo: kubernetes
prs: true
regexp: ^kind/
- missing_label: do-not-merge/needs-sig
org: kubernetes
repo: kubernetes
prs: true
regexp: ^(sig|wg|committee)/
# Define needs-sig separately for issues so that we only comment on issues.
- missing_label: needs-sig
org: kubernetes
repo: kubernetes
issues: true
regexp: ^(sig|wg|committee)/
missing_comment: |
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`
Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and committees available.
# Needs triage configuration
- missing_label: needs-triage
org: kubernetes
repo: kubernetes
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes
repo: website
issues: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the `triage/accepted` label.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes
repo: kubectl
issues: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the `triage/accepted` label.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes
repo: cloud-provider-gcp
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If the repository mantainers determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-sig
org: kubernetes
repo: community
issues: true
regexp: ^(sig|wg|committee)/
missing_comment: |
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`
Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and committees available.
- missing_label: needs-sig
org: kubernetes
repo: enhancements
issues: true
regexp: ^(sig|wg|committee)/
missing_comment: |
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`
Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and committees available.
- missing_label: needs-sig
org: kubernetes-sigs
repo: contributor-playground
issues: true
regexp: ^(sig|wg|committee)/
missing_comment: |
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`
Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and committees available.
- missing_label: needs-priority
org: kubernetes
repo: kubernetes
prs: true
regexp: ^priority/
- missing_label: needs-kind
org: kubernetes
repo: cloud-provider-aws
prs: true
regexp: ^kind/
- missing_label: needs-kind
org: kubernetes
repo: release
issues: true
prs: true
regexp: ^kind/
- missing_label: needs-priority
org: kubernetes
repo: release
issues: true
prs: true
regexp: ^priority/
- missing_label: needs-kind
org: kubernetes
repo: sig-release
issues: true
prs: true
regexp: ^kind/
- missing_label: needs-priority
org: kubernetes
repo: sig-release
issues: true
prs: true
regexp: ^priority/
- missing_label: needs-kind
org: kubernetes-client
repo: python
prs: true
regexp: ^kind/
- missing_label: needs-kind
org: kubernetes-client
repo: python-base
prs: true
regexp: ^kind/
- missing_label: needs-triage
org: kubernetes
repo: ingress-nginx
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-kind
org: kubernetes
repo: ingress-nginx
issues: true
prs: true
regexp: ^kind/
- missing_label: needs-priority
org: kubernetes
repo: ingress-nginx
issues: true
prs: true
regexp: ^priority/
- missing_label: needs-kind
org: kubernetes-sigs
repo: kustomize
issues: true
prs: false
regexp: ^kind/
- missing_label: needs-triage
org: kubernetes-sigs
repo: kustomize
issues: true
prs: false
regexp: ^triage/
missing_comment: |
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the `triage/accepted` label.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-priority
org: kubernetes-sigs
repo: cluster-api-provider-aws
issues: true
prs: true
regexp: ^priority/
- missing_label: do-not-merge/needs-area
org: kubernetes-sigs
repo: cluster-api
issues: false
prs: true
regexp: ^area/
missing_comment: |
This PR is currently missing an area label, which is used to identify the modified component when generating release notes.
Area labels can be added by org members by writing `/area ${COMPONENT}` in a comment
Please see the [labels list](https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.md#labels-that-apply-to-kubernetes-sigscluster-api-for-both-issues-and-prs) for possible areas.
- missing_label: needs-triage
org: kubernetes-sigs
repo: cluster-api
issues: true
prs: false
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If CAPI contributors determines this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes-sigs
repo: cluster-api-operator
issues: true
prs: false
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes-sigs
repo: cluster-api-provider-aws
issues: true
prs: false
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: do-not-merge/needs-kind
org: kubernetes-sigs
repo: cloud-provider-azure
prs: true
regexp: ^kind/
- missing_label: needs-sig
org: kubernetes
repo: test-infra
issues: true
regexp: ^(sig|wg|committee)/
missing_comment: |
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`
Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and committees available.
- missing_label: needs-triage
org: kubernetes
repo: cloud-provider-aws
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes-sigs
repo: custom-metrics-apiserver
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If custom-metrics-apiserver contributors determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes-sigs
repo: instrumentation-addons
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If instrumentation-addons contributors determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes-sigs
repo: instrumentation-tools
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If instrumentation-tools contributors determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes
repo: klog
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If klog contributors determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.
The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.
- missing_label: needs-triage
org: kubernetes
repo: kube-state-metrics
issues: true
prs: true
regexp: ^triage/accepted$
missing_comment: |
This issue is currently awaiting triage.
If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.