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.

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

start using kube-proxy v1alpha2 configuration in kubeadm #3027

Open
neolit123 opened this issue Feb 21, 2024 · 3 comments
Open

start using kube-proxy v1alpha2 configuration in kubeadm #3027

neolit123 opened this issue Feb 21, 2024 · 3 comments
Assignees
Labels
area/kube-proxy kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@neolit123
Copy link
Member

neolit123 commented Feb 21, 2024

kube-proxy v1alpha2 is WIP, we should track it and see when we can add support:

it's not very urgent for us, but i think our users will likely start requesting it as soon as its supported by kube-proxy.

@neolit123 neolit123 added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/feature Categorizes issue or PR as related to a new feature. area/kube-proxy labels Feb 21, 2024
@neolit123 neolit123 added this to the v1.30 milestone Feb 21, 2024
@neolit123 neolit123 modified the milestones: v1.30, v1.31 Apr 5, 2024
@neolit123 neolit123 self-assigned this Jun 5, 2024
@neolit123
Copy link
Member Author

plan for kube-proxy CC migration proposed here:
#1681 (comment)

@neolit123
Copy link
Member Author

asked the Q when v1alpha1 is planned for removal here:
kubernetes/kubernetes#121830 (review)

@neolit123 neolit123 modified the milestones: v1.31, v1.32 Aug 7, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue 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 Nov 5, 2024
@neolit123 neolit123 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 5, 2024
@neolit123 neolit123 modified the milestones: v1.32, v1.33 Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kube-proxy kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

3 participants