Updated Networking Requirements for Vsphere IPI

[dpateriya]

Hello Team,

I have updated the Networking Requirement section of the Vsphere Installation.

For more info, please check the relevant BZ[1] and Doc[2]. The above PR is for OCP 4.8+

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1821667
[2] https://github.com/openshift/installer/blob/master/docs/user/metal/install_ipi.md

[dpateriya]

cc @codyhoag

[netlify]

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 5936c34

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61e181c2cdab6f0008ae9ac3

😎 Browse the preview: https://deploy-preview-40594--osdocs.netlify.app

[bergerhoffer]

The branch/enterprise-4.11 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.10. And any PR going into main must also target the latest version branch (enterprise-4.11).

If the update in your PR does NOT apply to version 4.11 onward, please retarget this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[kalexand-rh]

@mjpytlak, will you PTAL?

[mjpytlak]

@mjpytlak, will you PTAL?

Happy to @kalexand-rh. Please be more specific. I do not see a eng/QE ack on this.

[mjpytlak]

Doc preview:

VMware vSphere infrastructure requirements > DNS records.

[mjpytlak]

@rvanderp3 Support is requesting that we update the vSphere doc. Who from engineering could take a look at the requested update? Also, @jinyunma are you the correct QE contact for this? If not, please forward to the correct contact. Thanks in advance.

[jinyunma]

Here cnf10, cnf11 are cluster name, suggest to describe the usage of podman command. For example:
$ podman run quay.io/openshift/origin-baremetal-runtimecfg:[TAG] vr-ids [CLUSTER_NAME]

[kalexand-rh]

@dpateriya, will you please update your PR?

[jinyunma]

And I reviewed similar update in #43599 before, which is in open status, maybe only need to get one of them merged?

[rvanderp3]

@rvanderp3 Support is requesting that we update the vSphere doc. Who from engineering could take a look at the requested update? Also, @jinyunma are you the correct QE contact for this? If not, please forward to the correct contact. Thanks in advance.

cc: @jcpowermac

@cybertron is this procedure relevant for 4.11 in light of openshift/machine-config-operator#3016 ?

[cybertron]

@cybertron is this procedure relevant for 4.11 in light of openshift/machine-config-operator#3016 ?

Good catch, it should not be necessary to check for vrid collisions in 4.11 on any platform. Still a good idea on 4.10 and earlier though.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[bergerhoffer]

The enterprise-4.12 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.11. And any PR going into main must also target the latest version branch (enterprise-4.12).

If the update in your PR does NOT apply to version 4.12 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.