Verifying Deployment Health

Page last updated:

This topic describes how to verify the health of your Pivotal Container Service (PKS) deployment.

Verify Kubernetes Health

Verify the health of your Kubernetes environment by following the steps below:

  1. To verify that all nodes are in a ready state, run the following command for all Kubernetes contexts:

    kubectl get nodes
    
  2. To verify that all pods are running, run the following command for all Kubernetes contexts:

    kubectl get pods --all-namespaces
    
  3. To verify that all the processes are in a running state, run the following command for each deployment:

    bosh -d MY-DEPLOYMENT instances --ps
    

    Where MY-DEPLOYMENT is the name of your PKS deployment. PKS deployment names begin with pivotal-container-service and include a unique BOSH-generated hash.

    For example:

    $ bosh -d pivotal-container-service/a1b2c333d444e5f66a77 instances --ps

Verify NCP Health (NSX-T Only)

NCP runs as a BOSH host process. Each Kubernetes master node VM has one NCP process running. If your cluster has multiple master nodes, one NCP process is active while the others are on standby. For more information, see Architectural Changes.

Verify NCP health by following the steps below:

  1. From the Ops Manager VM, run the following command:

    bosh -e MY-ENV login
    

    Where MY-ENV is the alias you set for your BOSH Director. For more information, see Managing PKS Deployments with BOSH.

    For example:

    $ bosh -e pks login

  2. To locate the Kubernetes master node VM name and ID, run the following command:

    bosh -e MY-ENV -d MY-DEPLOYMENT vms
    

    Where:

    • MY-ENV is the alias you set for your BOSH Director. For more information, see Managing PKS Deployments with BOSH.
    • MY-DEPLOYMENT is the name of your PKS deployment. PKS deployment names begin with pivotal-container-service and include a unique BOSH-generated hash.

    For example:

    $ bosh -e pks -d pivotal-container-service/a1b2c333d444e5f66a77 vms
    Your PKS API VM name begins with pivotal-container-service and includes a BOSH-generated hash. This value is different from the deployment hash.

  3. To SSH into the Kubernetes master node VM, run the following command:

    bosh -e MY-ENV -d MY-DEPLOYMENT ssh VM-NAME/ID
    

    Where:

    • MY-ENV is the alias you set for your BOSH Director. For more information, see Managing PKS Deployments with BOSH.
    • MY-DEPLOYMENT is the name of your PKS deployment. PKS deployment names begin with pivotal-container-service and include a unique BOSH-generated hash.
    • VM-NAME is your Kubernetes master node VM name.
    • ID is your Kubernetes master node VM ID. This is a unique BOSH-generated hash.

    For example:

    $ bosh -e pks \
    -d pivotal-container-service/a1b2c333d444e5f66a77 \
    ssh pivotal-container-service/000a1111-222b-3333-4cc5-de66f7a8899b

  4. From the master node VM, run the following command:

    monit summary
    

    Verify that you see Process: 'ncp' is running.

  5. To check if the NCP process is active or on standby, run the following command:

    /var/vcap/jobs/ncp/bin/nsxcli -c get ncp-master status
    
  6. To restart the NCP process, run the following command:

    monit restart ncp
    
  7. To verify that the NCP process restarts successfully, run the following command: monit summary


Please send any feedback you have to pks-feedback@pivotal.io.