OSDOCS#42796: Fixing the default value of macspoofchk#78823
OSDOCS#42796: Fixing the default value of macspoofchk#78823skopacz1 merged 1 commit intoopenshift:mainfrom
Conversation
|
🤖 Thu Aug 01 13:20:34 - Prow CI generated the docs preview: |
|
/label peer-review-needed |
agantony
left a comment
There was a problem hiding this comment.
Added a comment for your consideration; overall lgtm!
| <4> The actual name of the Container Network Interface (CNI) plugin that provides the network for this network attachment definition. Do not change this field unless you want to use a different CNI. | ||
| <5> The name of the Linux bridge configured on the node. | ||
| <6> Optional: Flag to enable MAC spoof check. When set to `true`, you cannot change the MAC address of the pod or guest interface. This attribute provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod. | ||
| <6> Optional: A flag to enable MAC spoof check. When set to `true`, you cannot change the MAC address of the pod or guest interface. This attribute provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod. |
There was a problem hiding this comment.
| <6> Optional: A flag to enable MAC spoof check. When set to `true`, you cannot change the MAC address of the pod or guest interface. This attribute provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod. | |
| <6> Optional: A flag to enable the MAC spoof check. When set to `true`, you cannot change the MAC address of the pod or guest interface. This attribute provides security against a MAC spoofing attack because only a single MAC address can exit the pod. |
There was a problem hiding this comment.
Hi Agil, thank you for the review! You're right about the definite article, but I would not change the final clause. The wording you suggested could imply that only a single MAC address being able to exit the pod is a general state, rather than something you config.
Thanks again,
J.
There was a problem hiding this comment.
OK, how about a lil bit more tweaking to avoid passive voice?
s/ "A flag to enable MAC spoof check. If set to true, you cannot change the MAC address of the pod or guest interface. This attribute only lets a single MAC address to exit the pod, which provides security against a MAC spoofing attack."
There was a problem hiding this comment.
Well, This attribute provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod. does not really contain a passive voice voice, AFAICT, but you're right that reordering the clauses makes it easier to read and comprehend. Thanks!
|
/remove-label peer-review-in-progress |
|
@agantony: Those labels are not set on the issue: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
New changes are detected. LGTM label has been removed. |
Applied peer review changes
|
/label merge-request-needed |
|
@jherrman: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@jherrman: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/label merge-review-needed |
|
/cherrypick enterprise-4.14 |
|
/cherrypick enterprise-4.15 |
|
/cherrypick enterprise-4.16 |
|
/cherrypick enterprise-4.17 |
|
@skopacz1: new pull request created: #80072 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@skopacz1: new pull request created: #80073 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@skopacz1: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.15 from head openshift-cherrypick-robot:cherry-pick-78823-to-enterprise-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.15 and openshift-cherrypick-robot:cherry-pick-78823-to-enterprise-4.15"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"} DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@skopacz1: new pull request created: #80074 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherrypick enterprise-4.15 |
|
@skopacz1: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.15 from head openshift-cherrypick-robot:cherry-pick-78823-to-enterprise-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.15 and openshift-cherrypick-robot:cherry-pick-78823-to-enterprise-4.15"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"} DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherrypick enterprise-4.15 |
|
@skopacz1: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.15 from head openshift-cherrypick-robot:cherry-pick-78823-to-enterprise-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.15 and openshift-cherrypick-robot:cherry-pick-78823-to-enterprise-4.15"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"} DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Version(s):
4.15 and later, probably also 4.14
Issue:
https://issues.redhat.com/browse/CNV-42796
Link to docs preview:
https://78823--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/vm_networking/virt-connecting-vm-to-linux-bridge.html
QE review: