You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provision GCS (or the default cloud provider) buckets for logs with private access (SA) #9168
The SRC wants to setup CI for the private fork of Kubernetes. As discussed in sig-k8s-infra meetings, we'll use the same service cluster and provision a new build cluster with a private deck instance for running these jobs.
As the starting step, creating GCS (or the default cloud provider) storage buckets with appropriate access. Non world readable buckets, write and read access to Deck instance which would be behind an oauth2 proxy.
The SRC private organization: https://github.com/kubernetes-security already seems to have the github app for prow installed. (need to validate permissions)
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.
Activity
Vyom-Yadav commentedon Feb 5, 2026
Marko, as discussed on DMs, I've assigned this issue to you.
Vyom-Yadav commentedon Feb 5, 2026
/sig k8s-infra
BenTheElder commentedon Mar 2, 2026
/transfer k8s.io
k8s-triage-robot commentedon May 31, 2026
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot commentedon Jun 30, 2026
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
xmudrii commentedon Jul 1, 2026
This has been done
/close
kubernetes-prow commentedon Jul 1, 2026
@xmudrii: Closing this issue.
Details
In response to this:
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.