Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate the krel GCB jobs from kubernetes-release-test to a community owned project #3853

Closed
xmudrii opened this issue Dec 10, 2024 · 4 comments
Closed

Migrate the krel GCB jobs from kubernetes-release-test to a community owned project #3853

xmudrii opened this issue Dec 10, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@xmudrii
Copy link
Member

xmudrii commented Dec 10, 2024

We need to migrate the krel GCB jobs (e.g. release jobs and image build jobs) from the kubernetes-release-test GCP project to a community owned GCP project.

We yet need to determine:

  • What GCP project should we use
  • Do we have enough quotas
  • What references we need to change

I didn't see an issue for tracking this, so I'm creating a new one, if there's already a duplicate, please reference it and close this one.
@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Dec 10, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Dec 10, 2024

/priority important-soon
/kind feature

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/feature Categorizes issue or PR as related to a new feature. and removed needs-priority needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Dec 10, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Dec 10, 2024

Looks like some jobs are already using k8s-staging-releng project. @BenTheElder @kubernetes/release-engineering Any idea if we can use the same project for releases?

@xmudrii
Copy link
Member Author

xmudrii commented Dec 10, 2024

Actually we already have an issue for tracking this: #3425
I thought that it's about the bucket, not jobs, my bad. 🤦

/close

@k8s-ci-robot
Copy link
Contributor

@xmudrii: Closing this issue.

In response to this:

Actually we already have an issue for tracking this: #3425
I thought that it's about the bucket, not jobs, my bad. 🤦

/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
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xmudrii @k8s-ci-robot