forked from pivotal-cf/docs-pks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
diagnostic-tools.html.md.erb
40 lines (23 loc) · 1.31 KB
/
diagnostic-tools.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
---
title: Diagnostic Tools
owner: Ops Manager
---
##<a id='pks-cli'></a>Verify PKS CLI Version
The Pivotal Container Service (PKS) CLI interacts with the your PKS deployment through the PKS API endpoint. You create, manage, and delete Kubernetes clusters on your PKS deployment by entering commands in the PKS CLI. The PKS CLI is under active development and commands may change between versions.
To determine the version of PKS CLI installed locally, run the following command:
<pre>pks --version</pre>
For example:
<pre class="terminal">$ pks --version
PKS CLI version: 1.0.0-build.3</pre>
## <a id='pks-api'></a>SSH into the PKS VM
To SSH into the PKS VM using BOSH, follow the steps below:
<%= partial 'bosh-ssh' %>
##<a id='bosh-pks-map'></a>View Log Files
Log files contain error messages and other information you can use to diagnose issues with your PKS deployment. SSH into the PKS VM then follow the steps below to access PKS log files.
1. To act as super user on the PKS VM, run the following command:
<pre>sudo su</pre>
1. To navigate to the PKS VM's `/var/vcap/sys/log` log file directory, run the following command:
<pre>cd /var/vcap/sys/log</pre>
1. Examine the following files:
* On the PKS master VM, examine the `kube-apiserver` log file.
* On a PKS worker VM, examine the `kubelet` log file.