[enterprise-4.20] OSDOCS-16997-installation-config-parameters-gcp# CQA - #119206
Merged
sslocket merged 1 commit intoSep 3, 2026
Merged
Conversation
Contributor
Author
openshift-ci
Bot
added
the
size/XS
Contributor
Author
|
/retest |
|
🤖 Wed Sep 02 14:29:37 - Prow CI generated the docs preview: |
|
@sslocket: 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a manual cherry-pick of #114139 to enterprise-4.20.
The automated cherry-pick failed because of a merge conflict in
modules/installation-configuration-parameters.adoc. I resolved it manually to apply only the change from #114139 (thenetworking.machineNetworkNOTE phrasing). The AWS dual-stack networking content in that NOTE block exists onmainbut not on this branch, so it was correctly excluded from the resolution./assign sslocket