-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS-42088: updates RNs for Egress IPs additional nwts #81968
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
OCPBUGS-42088: updates RNs for Egress IPs additional nwts #81968
Conversation
|
@JoeAldinger: This pull request references Jira Issue OCPBUGS-42088, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
LGTM |
1 similar comment
|
LGTM |
|
cc @jechen0648 as @huiran0826 is on PTO |
|
LGTM |
|
/retest |
|
/lgtm |
|
@JoeAldinger: This pull request references Jira Issue OCPBUGS-42088, which is invalid:
Comment 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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Tue Sep 17 18:20:15 - Prow CI generated the docs preview: |
|
@JoeAldinger: 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. |
jldohmann
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.
lgtm. do we have a consensus on how to mark things as being generally available? i see it sometimes as "Generally Available", which is in line with how we denote things as "Technology Preview", but i see it more commonly as "generally available". either way, this is outside the scope of this PR 😄
|
@jldohmann my two cents on your doubt: "Generally Available" is often abbreviated GA the same way "Technology Preview" is often abbreviated TP, so I guess keeping the capital letters makes sense when we talk about the feature supportability status. But as you said, this is beyond the scope of the PR. |
|
LGTM |
|
@JoeAldinger: Jira Issue OCPBUGS-42088 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state. 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 openshift-eng/jira-lifecycle-plugin repository. |
Version(s):
4.14
Issue:
https://issues.redhat.com/browse/OCPBUGS-42088
Link to docs preview:
QE review:
Additional information:
4.15 PR
4.16 PR