k8s.io icon indicating copy to clipboard operation
k8s.io copied to clipboard

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites

Results 226 k8s.io issues
Sort by recently updated
recently updated
newest added

Add content-Team shadows in the summit-team group

cncf-cla: yes
lgtm
size/XS
sig/contributor-experience
area/access
area/groups
sig/k8s-infra

The following command generates `curl: (22) The requested URL returned error: 403` ```tty curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.30/deb/Release.key ```

kind/support
sig/release
needs-triage

This PR adds [Peter Schuurman](https://github.com/pwschuurman) to the k8s-infra-prow-viewers Google Group so that he can see resources in the GKE Prow build cluster. This is needed to access GCP VM logs...

cncf-cla: yes
size/XS
sig/testing
lifecycle/rotten
area/access
area/groups
sig/k8s-infra

Audit Updates sig-k8s-infra

cncf-cla: yes
size/XL
area/audit
sig/k8s-infra

- adding myself to the list as CAPI `release-1.9` CI signal lead: https://github.com/cahillsf/k8s.io/pull/new/update-capi-alerts - removing those on the list no longer on the release team

cncf-cla: yes
lgtm
size/XS
sig/cluster-lifecycle
area/access
area/groups
sig/k8s-infra

Drop all cookies and only all specific HTTP headers for any client request.

cncf-cla: yes
size/XS
do-not-merge/work-in-progress
approved
area/infra
sig/k8s-infra

Add config for vsphere CSI driver image promotion cc: @XudongLiuHarold @xing-yang

cncf-cla: yes
lgtm
size/L
area/artifacts
sig/k8s-infra
area/registry.k8s.io

I am working on-recreating a prow job and these prow jobs deleted during migration to community infra. [Discussion ref](https://groups.google.com/a/kubernetes.io/g/dev/c/p6PAML90ZOU). I started re-creation of the Job and submitted https://github.com/kubernetes/test-infra/pull/33340/files But when...

sig/k8s-infra

/cc @xing-yang @divyenpatel This has already been deployed.

cncf-cla: yes
size/M
approved
area/artifacts
area/infra
area/terraform
sig/k8s-infra
area/infra/gcp
area/registry.k8s.io

We didn't manage to utilize KubeCost to gather data about ProwJobs because ProwJobs are non-managed Pods (e.g. not part of a ReplicaSet/Deployment) and this is not supported well by KubeCost....

priority/important-longterm
area/infra
sig/k8s-infra
area/infra/aws