Customer-provided networks in ShiftStack installation - OSDOCS#22186
Customer-provided networks in ShiftStack installation - OSDOCS#22186maxwelldb merged 4 commits intoopenshift:masterfrom
Conversation
|
At the moment, this PR just adds the relevant param w/a commented question. Unsure about additional work required at this point. |
f3e32e1 to
4d8f477
Compare
|
The preview will be available shortly at: |
|
Relevant: openshift/installer#3647 |
|
Also relevant: openshift/installer@fb30018 |
0130b79 to
69453f8
Compare
|
@iamemilio I chunked off the content into its own module--it was getting a bit much for the properties table. Questions:
|
b4ef0fe to
1c1c447
Compare
1c1c447 to
c53757e
Compare
|
lgtm |
3dd7573 to
557104b
Compare
557104b to
3663f6a
Compare
|
@wjiangjay or @gpei I have another PR for your review. Thanks! And in other OSP assemblies. |
|
@morenod Thanks! |
bobfuru
left a comment
There was a problem hiding this comment.
A few small nits; otherwise, LGTM.
|
@bobfuru Thanks! |
|
/cherry-pick enterprise-4.5 |
|
@maxwelldb: new pull request created: #23427 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/test-infra repository. |
|
@vikram-redhat I forgot to squash this pre-merge. 👎 What's the preferred strategy for fixing this in |
Sorry, I noticed the commits after my LGTM but didn't mention it because I thought it was primarily a practice we use to make it easier for reviewers to follow updates. Curious to hear if there are other reasons as well. |
|
@bobfuru Yeah, I've always avoided squashing until the last second to (maybe) make reviewing easier. My goof. |
The second last option.. leave it and let's not do it again :) |
Context: https://issues.redhat.com/browse/OSDOCS-1023