OSDOCS-1770 Installing a cluster on GCP in a restricted network

[codyhoag]

https://issues.redhat.com/browse/OSDOCS-1770

Previews:

• Installing a cluster on GCP in a restricted network
• Support matrix update

[netlify]

Deploy preview for osdocs ready!

Built with commit f591cba

https://deploy-preview-32482--osdocs.netlify.app

[codyhoag]

@staebler PTAL. I followed a similar path as what was recommended for AWS. Thanks!

[staebler]

LGTM

[codyhoag]

@tsze-redhat can you confirm from a QE perspective? Thanks!

[tsze-redhat]

Is this for adding a page for IPI Restricted cluster?

Assuming it is,
1 why do we need an existing vpc?

2 Item 12 in
https://deploy-preview-32482--osdocs.netlify.app/openshift-enterprise/latest/installing/installing_gcp/installing-restricted-networks-gcp-installer-provisioned.html#installation-gcp-config-yaml_installing-restricted-networks-gcp-installer-provisioned

under
additionalTrustBundle: |
-----BEGIN CERTIFICATE-----
<MY_TRUSTED_CA_CERT>
-----END CERTIFICATE-----

texts need to have two spaces from beginning.

Right now, there appears to be 4.

Can you confirm?

3 Hyperthreading for compute under
compute:

• hyperthreading: Enabled

is marked as remark #3 only but it should be #3 & #4 (similar to control).

4 Configuring the cluster-wide proxy during installation should be optional
https://deploy-preview-32482--osdocs.netlify.app/openshift-enterprise/latest/installing/installing_gcp/installing-restricted-networks-gcp-installer-provisioned.html#installation-configure-proxy_installing-restricted-networks-gcp-installer-provisioned

In fact, why do we have this section?
It is not there in Restricted network UPI page.

This section only appears in "Installing a cluster on GCP into an existing VPC" page.

Please feel free to ping me if you need any clarification on any of the above.

Thanks.

[codyhoag]

@tsze-redhat a few answers below:

Is this for adding a page for IPI Restricted cluster?

Yes

1. why do we need an existing vpc?

Matthew explained it well here. A snippet from his explanation to me: The point of needing to BYO VPC is that either (1) the mirror registry needs to be in the VPC or (2) the VPC needs to have firewall rules or peering to access the mirror registry hosted elsewhere. In either case, the VPC needs to exist before installation.

2. texts need to have two spaces from beginning. Right now, there appears to be 4.

Fixed

3. Hyperthreading for compute is marked as remark Initial build system #3 only but it should be Initial build system #3 & Fixed doc files to meet AsciiDoctor standards #4 (similar to control).

Fixed

4. Configuring the cluster-wide proxy during installation should be optional. In fact, why do we have this section? It is not there in Restricted network UPI page.

I've been putting this in the restricted assemblies based on feedback I receieved during the vSphere review process from Jinyun here. From what I understand, this used to not be supported for IPI installs, but is now supported as of recently. I'm not sure why it is not there for GCP UPI, but I can add it there in a separate PR if that would be relevant there.

Let me know if there's any other feedback or any changes for this. Thanks!

[tsze-redhat]

Given that user must provide vpc,
6, 7, 8 in https://deploy-preview-32482--osdocs.netlify.app/openshift-enterprise/latest/installing/installing_gcp/installing-restricted-networks-gcp-installer-provisioned.html#installation-gcp-config-yaml_installing-restricted-networks-gcp-installer-provisioned
should not begin with "If you use an existing VPC, "

The rest is good.

Thanks.

[maxwelldb]

Looks copacetic.

I made a few comments/suggestions, but nothing major.

The list punctuation thing should be resolved prior to merging.

[codyhoag]

/cherrypick enterprise-4.8

[codyhoag]

/cherrypick enterprise-4.7

[codyhoag]

/cherrypick enterprise-4.6

[codyhoag]

/cherrypick enterprise-4.5

[openshift-cherrypick-robot]

@codyhoag: new pull request created: #32510

In response to this:

/cherrypick enterprise-4.8

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.

[openshift-cherrypick-robot]

@codyhoag: new pull request created: #32511

In response to this:

/cherrypick enterprise-4.7

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.

[openshift-cherrypick-robot]

@codyhoag: #32482 failed to apply on top of branch "enterprise-4.6":

Applying: Installing a cluster on GCP in a restricted network
Using index info to reconstruct a base tree...
M	_topic_map.yml
A	installing/installing-preparing.adoc
M	modules/cli-installing-cli.adoc
M	modules/cluster-entitlements.adoc
M	modules/installation-about-restricted-network.adoc
M	modules/installation-configuration-parameters.adoc
M	modules/installation-configure-proxy.adoc
M	modules/installation-gcp-config-yaml.adoc
M	modules/installation-initializing.adoc
M	modules/ssh-agent-using.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/ssh-agent-using.adoc
Auto-merging modules/installation-initializing.adoc
Auto-merging modules/installation-gcp-config-yaml.adoc
CONFLICT (content): Merge conflict in modules/installation-gcp-config-yaml.adoc
Auto-merging modules/installation-configure-proxy.adoc
Auto-merging modules/installation-configuration-parameters.adoc
Auto-merging modules/installation-about-restricted-network.adoc
Auto-merging modules/cluster-entitlements.adoc
Auto-merging modules/cli-installing-cli.adoc
CONFLICT (modify/delete): installing/installing-preparing.adoc deleted in HEAD and modified in Installing a cluster on GCP in a restricted network. Version Installing a cluster on GCP in a restricted network of installing/installing-preparing.adoc left in tree.
Auto-merging _topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Installing a cluster on GCP in a restricted network
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.6

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.

[openshift-cherrypick-robot]

@codyhoag: #32482 failed to apply on top of branch "enterprise-4.5":

Applying: Installing a cluster on GCP in a restricted network
Using index info to reconstruct a base tree...
M	_topic_map.yml
A	installing/installing-preparing.adoc
M	modules/cli-installing-cli.adoc
M	modules/cli-logging-in-kubeadmin.adoc
M	modules/cluster-entitlements.adoc
M	modules/installation-about-restricted-network.adoc
M	modules/installation-configuration-parameters.adoc
M	modules/installation-configure-proxy.adoc
M	modules/installation-gcp-config-yaml.adoc
M	modules/installation-initializing.adoc
M	modules/installation-launching-installer.adoc
M	modules/ssh-agent-using.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/ssh-agent-using.adoc
Auto-merging modules/installation-launching-installer.adoc
Auto-merging modules/installation-initializing.adoc
Auto-merging modules/installation-gcp-config-yaml.adoc
CONFLICT (content): Merge conflict in modules/installation-gcp-config-yaml.adoc
Auto-merging modules/installation-configure-proxy.adoc
Auto-merging modules/installation-configuration-parameters.adoc
Auto-merging modules/installation-about-restricted-network.adoc
CONFLICT (content): Merge conflict in modules/installation-about-restricted-network.adoc
Auto-merging modules/cluster-entitlements.adoc
Auto-merging modules/cli-logging-in-kubeadmin.adoc
Auto-merging modules/cli-installing-cli.adoc
CONFLICT (modify/delete): installing/installing-preparing.adoc deleted in HEAD and modified in Installing a cluster on GCP in a restricted network. Version Installing a cluster on GCP in a restricted network of installing/installing-preparing.adoc left in tree.
Auto-merging _topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Installing a cluster on GCP in a restricted network
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.5

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.