Red Hat Bugzilla – Bug 978597
non-scaled applications cannot expose ports externally
Last modified: 2015-06-12 15:18:46 EDT
Description of problem:
According to the cartridge writers guide, you can expose an external port on a gear by adding an endpoint in the manifest with Public-Port-Name property. This works for scaled apps, but it does not appear that expose-port is called for non-scaled apps.
Steps to Reproduce:
1. Copy DIY cart to create a new cartridge
2. Add Endpoint at the end of the manifest.yml:
- Private-IP-Name: IP
3. Create an app using this cartridge
OPENSHIFT_DIY_EXTRA_PORT is defined but OPENSHIFT_DIY_EXTRA_PROXY_PORT is not and in the mcollective logs, expose-port is never invoked.
expose-port is invoked and OPENSHIFT_DIY_EXTRA_PROXY_PORT is given an external port number.
Demonstrated with my example https://github.com/sosiouxme/diy-extra-port-cartridge/blob/master/metadata/manifest.yml via the cartridge reflector...