Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

1. - [x ] Mandatory Add the required version to the Fix version/s field.

2. - [x ] Mandatory Choose the type of documentation change.

      - [ x] New topic in an existing section or new section
      - [ ] Update to an existing topic

3. - [ x] Mandatory for GA content:
            
       - [x ] Add steps and/or other important conceptual information here:

Currently needed firewall ports are distributed per component in various tables across the
 Networking guide (https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html-single/networking/) which makes it really hard for customers to understand at a glance what they need to configure on their firewalls and which port is needed by which component in which direction.

Hence it would be much better to have one picture showing all the components on hub and spoke clusters, their communication direction and needed open ports to have a one stop shop outlining all networking/fw requirements.