Bug 1322121

On the "Red Hat Enterprise Linux Atomic Host 7 Getting Started with Containers" documentation page, in section 2.3.3 Launching container pods with Kubernetes the example yaml files for the replication controllers are missing the host port specifications that will allow the web server and db server to be accessible from the host os when launched from Kubernetes.

In the red-hat-enterprise-linux-atomic-host/version-7/getting-started-guide/, the images are built exposing the ports from the Dockerfile, then run with 'docker run -p' to map them to the host ports.  When Kubernetes runs them, the option for a host port is not specified in the yaml, so the web server is not available from the host OS.

Suggested change to the files (just the hostPort parameter added under containerPort in the containers section:

[cloud-user@atomic01 yamlfiles]$ more db-rc.yaml 
apiVersion: v1
kind: ReplicationController
metadata:
  name: db-controller
spec:
  replicas: 1
  selector:
    app: "db"
  template:
    metadata:
      name: "db"
      labels:
        app: "db"
    spec:
      containers:
      - name: "db"
        image: "dbforweb"
        ports:
        - containerPort: 3306
          hostPort: 3306
[cloud-user@atomic01 yamlfiles]$ more webserver-rc.yaml 
kind: "ReplicationController"
apiVersion: "v1"
metadata:
  name: "webserver-controller"
spec:
  replicas: 1
  selector:
    name: "webserver"
  template:
    spec:
      containers:
        - name: "apache-frontend"
          image: "webwithdb"
          ports:
            - containerPort: 80
              hostPort: 80
    metadata:
      labels:
        name: "webserver"
        uses: db
[cloud-user@atomic01 yamlfiles]$