-
Notifications
You must be signed in to change notification settings - Fork 7
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
Remove -nodeport discovery configmap #765
Labels
Comments
Looks like we never actually deprecated this properly back in 24.11. I would propose rescheduling it for deprecation in 25.3 and removal in 25.3+1. |
Makes sense. Thanks for catching it. I agree with the proposal. |
nightkr
added a commit
that referenced
this issue
Jan 22, 2025
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 23, 2025
* Document -nodeport discovery as deprecated See #765 * Add deprecation warning to -nodeport discovery configmaps * Changelog * Fix import warning
Marking this as "done" since #813 is merged, but we shouldn't close it before it's removed as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's redundant now that #443 (24.11) brings first-class NodePort support. The primary discovery CM will now automatically adapt to the selected ListenerClass.
Deprecation schedule:
Users are encouraged to replace all uses with the primary discovery CM after upgrading to 24.11.
The text was updated successfully, but these errors were encountered: