Hide Forgot
Document ------------------- Name: RED HAT ENTERPRISE LINUX ATOMIC HOST 7 GETTING STARTED WITH CONTAINERS URL: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/ The kubernetes db-service is unable to find the pods deployed by the replication controller because the db-service.yaml file has an incorrect selector. The selector should be "app: db" instead of "name: db" (see below for the correct file content) db-service.yaml ------------------- apiVersion: v1 kind: Service metadata: labels: name: db name: db-service namespace: default spec: ports: - port: 3306 selector: app: db db-service.yaml is referenced in section "2.3.3 Launching container pods with Kubernetes" and "3.7. LAUNCHING SERVICES, REPLICATION CONTROLLERS, AND CONTAINER PODS WITH KUBERNETES". It is also included in kube_files.tar which is linked on the site. There are inconsistencies between the contents of the yaml files displayed in the documentation and kube_files.tar. They should be identical.
I changed name: db to app: db in the document, as described earlier. Once published, the fix can be found here: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#get_started_orchestrating_containers_with_kubernetes
Thanks Chris. This fix can be verified in section 3.3.3 here [1]. Moving this bug to CLOSED-->CURRENTRELEASE. [1] https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#launching_container_pods_with_kubernetes