Remove outdated information about k8s mixed protocol support#2228
Merged
fedepaol merged 1 commit intometallb:mainfrom Feb 15, 2024
Merged
Remove outdated information about k8s mixed protocol support#2228fedepaol merged 1 commit intometallb:mainfrom
fedepaol merged 1 commit intometallb:mainfrom
Conversation
Member
|
@renklus mind signing the commit (and thanks for the contribution!)? |
k8s now supports mixed protocol services of type LoadBalancer Coauthored-by: Federico Paolinelli <fpaoline@redhat.com> Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Member
|
Took the liberty to sign up the commit and to do a small change. Thanks again! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
k8s now supports mixed protocol services of type LoadBalancer
Mixed protocol support was merged in k8s with kubernetes/pull/94028.
Thanks for sending a pull request! A few things before we get started:
issue first, and get
agreement that the change is a good idea, and a general guideline
for how it should be implemented, before sending code. Large PRs
that weren't first discussed and agreed upon in an issue won't be
accepted.
#" in the PR text, so that the bug auto-closes when
the PR is merged.