Skip to content

Provision GCS (or the default cloud provider) buckets for logs with private access (SA) #9168

Closed

Description

@Vyom-Yadav

Part of #7588

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.

https://docs.prow.k8s.io/docs/getting-started-deploy/#configure-a-gcs-bucket
https://docs.prow.k8s.io/docs/private-deck/#2-operator-create-a-new-service-account-and-bind-it

The SRC private organization: https://github.com/kubernetes-security already seems to have the github app for prow installed. (need to validate permissions)

/assign @xmudrii

Activity

  1. added
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Feb 5, 2026
  2. Vyom-Yadav commented on Feb 5, 2026

    @Vyom-Yadav
    MemberAuthor

    Marko, as discussed on DMs, I've assigned this issue to you.

  3. Vyom-Yadav commented on Feb 5, 2026

    @Vyom-Yadav
    MemberAuthor

    /sig k8s-infra

  4. added
    sig/k8s-infraCategorizes an issue or PR as relevant to SIG K8s Infra.
    and removed
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Feb 5, 2026
  5. BenTheElder commented on Mar 2, 2026

    @BenTheElder
    Member

    /transfer k8s.io

  6. k8s-triage-robot commented on May 31, 2026

    @k8s-triage-robot

    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/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was 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

  7. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 31, 2026
  8. k8s-triage-robot commented on Jun 30, 2026

    @k8s-triage-robot

    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:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue as fresh with /remove-lifecycle rotten
    • Close this issue with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle rotten

  9. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 30, 2026
  10. xmudrii commented on Jul 1, 2026

    @xmudrii
    Member

    This has been done
    /close

  11. kubernetes-prow commented on Jul 1, 2026

    @kubernetes-prow
    Contributor

    @xmudrii: Closing this issue.

    Details

    In response to this:

    This has been done
    /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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.sig/k8s-infraCategorizes an issue or PR as relevant to SIG K8s Infra.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions