Skip to content

Comments

Create a staging repo for kubernetes-sigs/cluster-capacity#7030

Merged
k8s-ci-robot merged 1 commit intokubernetes:mainfrom
ingvagabund:staging-repo-for-cluster-capacity
Sep 23, 2025
Merged

Create a staging repo for kubernetes-sigs/cluster-capacity#7030
k8s-ci-robot merged 1 commit intokubernetes:mainfrom
ingvagabund:staging-repo-for-cluster-capacity

Conversation

@ingvagabund
Copy link
Contributor

@ingvagabund ingvagabund commented Jul 19, 2024

To enable container image builds from kubernetes-sigs/cluster-capacity.

Part of kubernetes-sigs/cluster-capacity#181

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 19, 2024
@k8s-ci-robot k8s-ci-robot requested review from dims and upodroid July 19, 2024 10:14
@k8s-ci-robot k8s-ci-robot added area/infra Infrastructure management, infrastructure design, code in infra/ area/infra/gcp Issues or PRs related to Kubernetes GCP infrastructure sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. labels Jul 19, 2024
@k8s-triage-robot
Copy link

k8s-triage-robot commented Oct 17, 2024

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 17, 2024
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Oct 18, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 18, 2024
@upodroid
Copy link
Member

upodroid commented Dec 4, 2024

Do we still need this?

@ingvagabund
Copy link
Contributor Author

ingvagabund commented Dec 5, 2024

Yes

@k8s-triage-robot
Copy link

k8s-triage-robot commented Mar 5, 2025

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 5, 2025
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Mar 5, 2025

@upodroid is there anything else I need to do to push this through?

@ingvagabund
Copy link
Contributor Author

ingvagabund commented Mar 5, 2025

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 5, 2025
@k8s-triage-robot
Copy link

k8s-triage-robot commented Jun 3, 2025

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 3, 2025
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Jun 11, 2025

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 11, 2025
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Jun 11, 2025

@upodroid PTAL

@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 9, 2025

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 9, 2025
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Sep 9, 2025

Still valid

@ingvagabund
Copy link
Contributor Author

ingvagabund commented Sep 9, 2025

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 9, 2025
@upodroid
Copy link
Member

upodroid commented Sep 18, 2025

Hi, please accept my apologies.

We updated the docs for the image promotion process and you can find it at https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/README.md

Please follow that doc and ping me on your PRs for approvals.

@ingvagabund
Copy link
Contributor Author

ingvagabund commented Sep 23, 2025

All good :) Thank you for sharing the steps. I will take a look to learn the new way.

@ingvagabund ingvagabund force-pushed the staging-repo-for-cluster-capacity branch from 17437ae to f170f14 Compare September 23, 2025 10:50
@k8s-ci-robot k8s-ci-robot added area/access Define who has access to what via IAM bindings, role bindings, policy, etc. area/groups Google Groups management, code in groups/ area/terraform Terraform modules, testing them, writing more of them, code in infra/gcp/clusters/ sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 23, 2025
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Sep 23, 2025

@upodroid I have followed the first step in https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/README.md#creating-staging-repos and updated this PR. Based on the steps this PR needs to be merged first. Then I can continue with the process. Is that correct?

@upodroid
Copy link
Member

upodroid commented Sep 23, 2025

Can you do the registries.tf in a separate PR?

@ingvagabund ingvagabund force-pushed the staging-repo-for-cluster-capacity branch from f170f14 to 217aca2 Compare September 23, 2025 12:36
@ingvagabund ingvagabund mentioned this pull request Sep 23, 2025
Merged
@ingvagabund
Copy link
Contributor Author

ingvagabund commented Sep 23, 2025

Done: #8550

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 23, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, upodroid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 23, 2025
@k8s-ci-robot k8s-ci-robot merged commit b234399 into kubernetes:main Sep 23, 2025
4 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.35 milestone Sep 23, 2025
@ingvagabund ingvagabund deleted the staging-repo-for-cluster-capacity branch September 24, 2025 10:47
@ingvagabund ingvagabund mentioned this pull request Sep 30, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@upodroid upodroid upodroid approved these changes

@dims dims Awaiting requested review from dims

Assignees

@upodroid upodroid

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/access Define who has access to what via IAM bindings, role bindings, policy, etc. area/groups Google Groups management, code in groups/ area/infra/gcp Issues or PRs related to Kubernetes GCP infrastructure area/infra Infrastructure management, infrastructure design, code in infra/ area/terraform Terraform modules, testing them, writing more of them, code in infra/gcp/clusters/ cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

v1.35

Development

Successfully merging this pull request may close these issues.

4 participants

@ingvagabund @k8s-triage-robot @upodroid @k8s-ci-robot