Skip to content

AAP-72950: Fix EE image pull destination in network ports table and diagrams#5969

Open
jklech-work wants to merge 1 commit intoansible:mainfrom
jklech-work:AAP-72950
Open

AAP-72950: Fix EE image pull destination in network ports table and diagrams#5969
jklech-work wants to merge 1 commit intoansible:mainfrom
jklech-work:AAP-72950

Conversation

@jklech-work
Copy link
Copy Markdown
Contributor

Summary

  • Fixes the network ports table row for execution node EE image pulls: destination changed from Automation Hub to Gateway
  • Execution nodes pull EE images through the Gateway proxy, not directly from Hub
  • Verified against aap-containerized-installer source code (execution_environments.py.j2, upload_images.yml)
  • Regenerated all 3 network architecture diagrams with the corrected connection
  • Added .drawio source files for future diagram maintenance (none existed before)

Changes

Network ports table (ref-network-ports-protocols-table.adoc):

  • Row for execution node EE image pull: destination changed from {HubNameStart} to {GatewayStart}
  • Description updated: "Allows execution nodes to pull the execution environment image from {HubName} through {Gateway}"

Architecture diagrams (all 3 regenerated):

  • network_client_initiated.png — RPM client-initiated
  • network_internally_initiated.png — RPM internally-initiated
  • Container-network_internally_initiated.png — Container-based

Jira: https://issues.redhat.com/browse/AAP-72950

Verification

  • aap-planning-guide builds successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant