-
Notifications
You must be signed in to change notification settings - Fork 632
describe TargetRefs conflict-resolution rules in BackendTLSPolicy #4048
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
describe TargetRefs conflict-resolution rules in BackendTLSPolicy #4048
Conversation
Signed-off-by: Norwin Schnyder <[email protected]>
a103fd2 to
456df51
Compare
|
Those rules LGTM, so I'll approve here, and leave the LGTM for someone else. /approve |
kl52752
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the change LGTM
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kl52752, snorwin, youngnick The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
…bernetes-sigs#4048) Signed-off-by: Norwin Schnyder <[email protected]>
What type of PR is this?
/kind documentation
What this PR does / why we need it:
During the discussions in #4043 we realized that the conflict-resolution rules for BackendTLSPolicy were missing in the API specification. To make this clearer for both implementers and users, this PR adds the conflict-resolution rules to the TargetRef description.
Which issue(s) this PR fixes:
N/A
Does this PR introduce a user-facing change?: