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

Audit code for Kubernetes-version specific handling #8190

Open
11 tasks
sbueringer opened this issue Feb 27, 2023 · 4 comments
Open
11 tasks

Audit code for Kubernetes-version specific handling #8190

sbueringer opened this issue Feb 27, 2023 · 4 comments
Assignees
@sbueringer
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbueringer
Copy link
Member

sbueringer commented Feb 27, 2023 •
edited
Loading

Goal of this issue is to audit all code in core Cluster API for Kubernetes version-specific handling and come up with an overview with which Kubernetes (and estimated Cluster API) version we can drop which code.

Tasks:

/kind cleanup
@sbueringer sbueringer added this to the v1.5 milestone Feb 27, 2023
@sbueringer sbueringer self-assigned this Feb 27, 2023
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 27, 2023
@sbueringer
Copy link
Member Author

I intentionally added this to the v1.5 milestone as we won't start this activity before then and it would be good to have for v1.5

This was referenced Feb 27, 2023
Closed
Closed
@fabriziopandini
Copy link
Member

/triage accepted
/help

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 20, 2023
@sbueringer
Copy link
Member Author

/remove-help

I'll be working on this one

@k8s-ci-robot k8s-ci-robot removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 21, 2023
@sbueringer sbueringer modified the milestones: v1.5, v1.6 Jun 21, 2023
@sbueringer sbueringer removed this from the v1.6 milestone Mar 12, 2024
@fabriziopandini
Copy link
Member

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 11, 2024
@sbueringer sbueringer mentioned this issue Sep 6, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbueringer sbueringer

Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbueringer @fabriziopandini @k8s-ci-robot