Repository navigation
Specify the usage of BackendTLSPolicy as a union feature - #4745
Merged
Merged
Conversation
rikatz
force-pushed
the
union-feature-api
branch
from
April 12, 2026 17:46
456710b to
8d964c3
Compare
Contributor
|
Thanks for this, very thorough! /lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz, snorwin The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Member
Author
|
/hold cancel |
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.
What type of PR is this?
/kind documentation
/kind feature
/kind gep
What this PR does / why we need it:
Specify the usage of BackendTLSPolicy as a union feature
Which issue(s) this PR fixes:
Fixes #4274
Does this PR introduce a user-facing change?:
Note: Per the new AI policy, disclosing that I have created all of the changes here and asked Claude Opus 4.6 to verify consistency and wording