Bug 1557462

Summary: Document limitations & workaround of the APB CLI tool working with a remote cluster
Product: OpenShift Container Platform Reporter: Dylan Murray <dymurray>
Component: DocumentationAssignee: Alex Dellapenta <adellape>
Status: CLOSED DUPLICATE QA Contact: Vikram Goyal <vigoyal>
Severity: high Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, dmoessne, jmatthew, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-02 21:41:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dylan Murray 2018-03-16 15:38:01 UTC 
Document URL: 
https://docs.openshift.com/container-platform/3.7/apb_devel/cli_tooling.html

Section Number and Name: 
New section: Current limitations/Troubleshooting (or something of the sort)

Describe the issue: 
When using the APB tool to use `apb push` for the development lifecycle, there is a known restriction when trying to push to a cluster that is not on the same host where the APB tool is being used. To workaround, you can use the --registry-route flag to push to an exposed registry. We have documented the workaround here: https://access.redhat.com/solutions/3309411. 

Suggestions for improvement: 
Please include a workaround section in the docs and include the above linked solution.
Comment 1 Alex Dellapenta 2021-08-02 21:41:34 UTC 

*** This bug has been marked as a duplicate of bug 1526147 ***