Bug 2233266

Summary: [DDF] This is confusing. This is the Satellite "outgoing" communication to itself? You have this everywhere in the
Product: Red Hat Satellite Reporter: Direct Docs Feedback <ddf-bot>
Component: InstallationAssignee: Aneta Šteflová Petrová <apetrova>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: agadhave, gsulliva, mjivraja
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 15:20:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-08-21 19:34:58 UTC
This is confusing. This is the Satellite "outgoing" communication to itself? You have this everywhere in the network tables, makes no sense.

Reported by: dennis.whintey

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/installing_satellite_server_in_a_connected_network_environment/preparing_your_environment_for_installation_satellite#annotations:5c2c64f7-dc53-4709-b974-83dbb9662896

Comment 2 Marie Hornickova 2023-08-22 09:02:51 UTC
Hello,
Many thanks for using the Direct Documentation feedback tool for providing feedback for documentation improvement.
The documentation team representative who will take this will share updates about the progress on its implementation in this ticket.
Thank you!

Comment 3 Griffin Sullivan 2023-08-24 13:00:36 UTC
This is something we should address and might require adding additional resources to the documentation like a diagram.

Comment 5 Aneta Šteflová Petrová 2023-09-20 09:59:54 UTC
(In reply to Griffin Sullivan from comment #3)
> This is something we should address and might require adding additional
> resources to the documentation like a diagram.

Griffin, can you please explain why the port needs to be open? I'd like to address this issue by adding an explanation somewhere in this section.

While adding a diagram is also an option, this would not be a good place for it. A more suitable place would be in the Overview guide, where we have other similar diagrams: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/satellite_overview_concepts_and_deployment_considerations/index#sect-Documentation-Architecture_Guide-Capsule_Networking
That said, I'm not convinced it would be a good idea to add another beast of a diagram like this one. They tend to be very overwhelming. Please let me know if you disagree.

Comment 7 Griffin Sullivan 2023-09-21 15:58:21 UTC
I'm fine with leaving the diagram out of this section.

Port 443 needs to be open because that is where Satellite and Pulp run. If they are not open, you will not be able to communicate with neither Satellite nor Pulp.

Comment 8 Aneta Šteflová Petrová 2023-09-22 09:59:46 UTC
PR submitted for review: https://github.com/theforeman/foreman-documentation/pull/2451

Comment 9 Aneta Šteflová Petrová 2023-09-22 14:33:43 UTC
PR merged: https://github.com/theforeman/foreman-documentation/pull/2451#issuecomment-1731174615