Bug 1573228

Summary: Need to EXPOSE port in golang s2i image so OpenShift properly reacts
Product: DevTools Reporter: Steve Speicher <sspeiche>
Component: go-toolset-7-containerAssignee: Derek Parker <deparker>
Status: CLOSED NOTABUG QA Contact: Edjunior Barbosa Machado <emachado>
Severity: high Docs Contact:
Priority: unspecified    
Version: go-toolset-7CC: deparker, jcajka, mnewsome, tstellar
Target Milestone: rc   
Target Release: 2018.2   
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: 2018-06-04 17:45:55 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 Steve Speicher 2018-04-30 14:27:34 UTC 
Description of problem:
OpenShift behaves differently when a port is exposed from a container via EXPOSE. For example, in the web console and oc new-app services and routes can be autocreated and provides a consistent and simple experience, like the other images.

See example from nodejs https://github.com/sclorg/s2i-nodejs-container/blob/master/8/Dockerfile#L6

Can we get EXPOSE 8080 added to the golang s2i image as well?