Skip to content

Remove legacy addons#17332

Merged
k8s-ci-robot merged 3 commits intokubernetes:masterfrom
rifelpet:delete-addons
Apr 10, 2025
Merged

Remove legacy addons#17332
k8s-ci-robot merged 3 commits intokubernetes:masterfrom
rifelpet:delete-addons

Conversation

@rifelpet
Copy link
Copy Markdown
Member

@rifelpet rifelpet commented Mar 28, 2025

These have been deprecated for 5 years. Anyone still using the channels command to apply manifests from this directory can update the path in the command arguments to reference an older kops release branch

Support for legacy addons was removed in kops clusters running k8s 1.23 #12064

/hold for feedback

@rifelpet
Remove legacy addons
f44547b 
These have been deprecated for 5 years. Anyone still using the channels command to apply manifests from this directory can update the path in the command arguments to reference an older kops release branch
@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Mar 28, 2025
@hakman
Copy link
Copy Markdown
Member

hakman commented Mar 28, 2025

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 28, 2025
@hakman
Copy link
Copy Markdown
Member

hakman commented Apr 1, 2025

/override tests-e2e-scenarios-bare-metal

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Apr 1, 2025

@hakman: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • tests-e2e-scenarios-bare-metal

Only the following failed contexts/checkruns were expected:

  • EasyCLA
  • build-linux-amd64
  • build-linux-arm64
  • build-macos-amd64
  • build-windows-amd64
  • deploy/netlify
  • pull-kops-build
  • pull-kops-e2e-k8s-aws-amazonvpc
  • pull-kops-e2e-k8s-aws-calico
  • pull-kops-e2e-k8s-gce-cilium
  • pull-kops-e2e-k8s-gce-ipalias
  • pull-kops-test
  • pull-kops-verify-boilerplate
  • pull-kops-verify-generated
  • pull-kops-verify-gofmt
  • pull-kops-verify-golangci-lint
  • pull-kops-verify-gomod
  • pull-kops-verify-govet
  • tide
  • verify-amd64
  • verify-arm64

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override tests-e2e-scenarios-bare-metal

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.

@hakman
Copy link
Copy Markdown
Member

hakman commented Apr 1, 2025

/override tests-e2e-scenarios-bare-metal

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Apr 1, 2025

@hakman: Overrode contexts on behalf of hakman: tests-e2e-scenarios-bare-metal

Details

In response to this:

/override tests-e2e-scenarios-bare-metal

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.

@hakman
Copy link
Copy Markdown
Member

hakman commented Apr 10, 2025

Should this be also added to release notes?
/approve

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Apr 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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 Apr 10, 2025
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 10, 2025
@rifelpet
Copy link
Copy Markdown
Member Author

rifelpet commented Apr 10, 2025

/unhold

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 10, 2025
@hakman
Copy link
Copy Markdown
Member

hakman commented Apr 10, 2025

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 10, 2025
@k8s-triage-robot
Copy link
Copy Markdown

k8s-triage-robot commented Apr 10, 2025

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-ci-robot k8s-ci-robot merged commit 886a0ef into kubernetes:master Apr 10, 2025
25 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.32 milestone Apr 10, 2025
@rifelpet rifelpet modified the milestones: v1.32, v1.33 Jun 23, 2025
@BrewTestBot BrewTestBot mentioned this pull request Oct 21, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hakman hakman Awaiting requested review from hakman

@johngmyers johngmyers Awaiting requested review from johngmyers

Assignees

@hakman hakman

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/documentation 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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Milestone

v1.33

Development

Successfully merging this pull request may close these issues.

4 participants

@rifelpet @hakman @k8s-ci-robot @k8s-triage-robot