Skip to content

Prepare for blixt image generation#7875

Closed
rikatz wants to merge 2 commits intokubernetes:mainfrom
rikatz:add-blixt-container-areas
Closed

Prepare for blixt image generation#7875
rikatz wants to merge 2 commits intokubernetes:mainfrom
rikatz:add-blixt-container-areas

Conversation

@rikatz
Copy link
Member

@rikatz rikatz commented Mar 13, 2025

This PR prepares for Blixt images publishing: kubernetes-retired/blixt#339

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/access Define who has access to what via IAM bindings, role bindings, policy, etc. area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/groups Google Groups management, code in groups/ labels Mar 13, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 13, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rikatz
Once this PR has been reviewed and has the lgtm label, please assign xmudrii for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 area/infra Infrastructure management, infrastructure design, code in infra/ area/infra/gcp Issues or PRs related to Kubernetes GCP infrastructure area/registry.k8s.io Code in registry.k8s.io/ sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/network Categorizes an issue or PR as relevant to SIG Network. labels Mar 13, 2025
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 13, 2025
@rikatz rikatz force-pushed the add-blixt-container-areas branch from 1d68f8f to b79f82d Compare March 13, 2025 22:19
@rikatz rikatz mentioned this pull request Mar 13, 2025
Closed
@ameukam
Copy link
Member

ameukam commented Mar 14, 2025

@rikatz Sorry for the docs on this but we changed the way we boostrap the AR repos. See #7750 as an example. Google groups are still needed.
cc @upodroid

@k8s-triage-robot
Copy link

k8s-triage-robot commented Jun 12, 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 12, 2025
@rikatz rikatz force-pushed the add-blixt-container-areas branch from b79f82d to f4796fd Compare June 19, 2025 20:53
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Jun 19, 2025 •
edited
Loading

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: rikatz / name: Ricardo Katz (1da6b9c)
  • ✅ login: plkokanov / name: Plamen Kokanov (e354304)

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. area/terraform Terraform modules, testing them, writing more of them, code in infra/gcp/clusters/ and removed cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jun 19, 2025
@rikatz rikatz force-pushed the add-blixt-container-areas branch from f4796fd to 1da6b9c Compare June 19, 2025 20:55
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Jun 19, 2025
@rikatz
Copy link
Member Author

rikatz commented Jun 19, 2025

@ameukam done, sorry, was busy, but am not anymore :P

ameukam
ameukam reviewed Jun 20, 2025
View reviewed changes
registry.k8s.io/images/k8s-staging-provider-aws/images.yaml
"sha256:73098fad2ebe298d356c1f595d19651e46d93ff7a5676c7533ff3c2632a6624c": ["v1.31.3"]
"sha256:47f861081efbc04bda32b6212ca2c74b5b2ce190e595a285e1b712ca0afec0c7": ["v1.31.4"]
"sha256:6f94a695828de888c8efc57e3243db9e788709767f687a6a8cb07c2e42158862": ["v1.31.5"]
"sha256:911a530d2166adb3af8b86e37320b138705bcffba5421a2280473dff9262b5cf": ["v1.31.6"]
Copy link
Member

@ameukam ameukam Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rebase when wrong ?

ameukam
ameukam reviewed Jun 20, 2025
View reviewed changes
infra/gcp/infra.yaml
k8s-staging-apisnoop:
k8s-staging-artifact-promoter:
k8s-staging-autoscaling:
k8s-staging-blixt:
Copy link
Member

@ameukam ameukam Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No longer needed I believe.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 4, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 4, 2025

PR needs rebase.

Details

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.

@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 3, 2025

The Kubernetes project currently lacks enough active 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 rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 3, 2025
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 2, 2025

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and 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:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 2, 2025

@k8s-triage-robot: Closed this PR.

Details

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and 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:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/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

Reviewers

@ameukam ameukam ameukam left review comments

@MadhavJivrajani MadhavJivrajani Awaiting requested review from MadhavJivrajani

@thockin thockin Awaiting requested review from thockin

Assignees

No one assigned

Labels

area/access Define who has access to what via IAM bindings, role bindings, policy, etc. area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects 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/registry.k8s.io Code in registry.k8s.io/ 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/network Categorizes an issue or PR as relevant to SIG Network. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@rikatz @k8s-ci-robot @ameukam @k8s-triage-robot @plkokanov