Red Hat Bugzilla – Bug 1313439
[DOCS] [7.3] [RFE] - use 'kubectl' commands to determine health of Kubernetes master services
Last modified: 2016-11-17 22:56:34 EST
In the docs for setting up a Kubernetes cluster , after the Kubernetes master services have been configured and started, the user could use the 'kubectl' command to test if they have been successful. This is more native to Kubernetes than inspecting the output of 'ps'
-bash-4.2# kubectl cluster-info
Kubernetes master is running at http://localhost:8080
-bash-4.2# kubectl get nodes
NAME LABELS STATUS AGE
master kubernetes.io/hostname=master Ready 22s
-bash-4.2# kubectl get services --all-namespaces=true
NAMESPACE NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
default kubernetes 10.254.0.1 <none> 443/TCP <none> 5m
-bash-4.2# kubectl get pods --all-namespaces=true
NAMESPACE NAME READY STATUS RESTARTS AGE
default kube-apiserver-master 1/1 Running 0 5m
default kube-controller-manager-master 1/1 Running 0 5m
default kube-scheduler-master 1/1 Running 0 5m
Good suggestions. I'll add those or similar commands to the chapter for Atomic/RHEL 7.3.
The particular chapter mentioned in this RFE has been dropped. However, I'm adding the kubectl commands suggested to the remaining Kubernetes (all-in-one) chapter (https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#get_started_orchestrating_containers_with_kubernetes). It will be published when RHEL 7.3 is released.
This is now covered in the Getting Started with Kubernetes guide: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/7/single/getting-started-with-kubernetes/
Moving this to CLOSED --> CURRENTRELEASE.