-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS-28912 Updating creating a Whereabouts reconciler daemon #72504
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
Conversation
🤖 Tue Mar 05 14:42:34 - Prow CI generated the docs preview: |
Hi @cgoncalves @liornoy when I was verifying #71081 i noticed the guidance in this section was not 100% accurate. Can you add a LGTM to this PR If happy with the change. |
/lgtm |
/label peer-review-needed |
/remove-label peer-review-needed |
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.
The YAML example seems like it could potentially cause issues if directly copy and pasted to me. Could we only include the specific information that's being talked about in the procedure?
/remove-label peer-review-in-progress
/label peer-review-done
+ | ||
[source,yaml] | ||
---- | ||
apiVersion: operator.openshift.io/v1 | ||
kind: Network | ||
metadata: | ||
creationTimestamp: "2024-01-03T11:19:12Z" |
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.
Personally, I wouldn't include this information in the example YAML file here. It's inviting potential user error with copy and paste in my opinion.
Is this information supposed to be written by hand or generated by a tool? I see references to a generation number, resource version, and UID, all of which are unlikely to be the same between what the user is doing and what the YAML example here displays.
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 @kowen-rh I am going to look at that again and maybe just detail the exact snippet of YAML that needs included
@@ -51,6 +55,7 @@ spec: | |||
} | |||
} | |||
type: Raw | |||
#... |
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.
Personally, I think it would be a good idea to include this type of comment directly before the spec:
key to imply that there is additional YAML both before and after the whereabouts-shim
that we're telling the user to include. Does that make sense?
New changes are detected. LGTM label has been removed. |
2f826a8
to
fb22c02
Compare
/label merge-review-needed |
apiVersion: operator.openshift.io/v1 | ||
kind: Network | ||
metadata: | ||
name: cluster |
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.
The doc guidelines require this section: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#required-fields
@kquinn1204 I have one comment that I am hoping you can consider before we merge. Reach out directly when ready. |
6af3c58
to
6b724b8
Compare
@kquinn1204: all tests passed! Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
Thank you @mburke5678 that is a good recommendation hopefully OK to merge now |
/cherrypick enterprise-4.12 |
/cherrypick enterprise-4.13 |
/cherrypick enterprise-4.14 |
/cherrypick enterprise-4.15 |
/cherrypick enterprise-4.16 |
@mburke5678: #72504 failed to apply on top of branch "enterprise-4.12":
In 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/test-infra repository. |
@mburke5678: new pull request created: #72625 In 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/test-infra repository. |
@mburke5678: new pull request created: #72626 In 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/test-infra repository. |
@mburke5678: new pull request created: #72627 In 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/test-infra repository. |
@mburke5678: new pull request created: #72628 In 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/test-infra repository. |
The affected file is not in enterprise-4.12. |
[OCPBUGS-28912]: Updating the guidance for adding the additionalNetworks section.
Version(s): 4.12, 4.13, 4.14, 4.15 and main
Issue: https://issues.redhat.com/browse/OCPBUGS-28912
Link to docs preview: https://72504--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/multiple_networks/configuring-additional-network.html#nw-multus-creating-whereabouts-reconciler-daemon-set_configuring-additional-network
QE review:
Additional information: