@@ -17,15 +17,6 @@ Orchestration systems like Kubernetes. To use this tool you must first create a
17
17
context with the appropriate information. ` px ` uses the context to connect to
18
18
the appropriate Portworx cluster to execute the requested command.
19
19
20
- ## Installing as a kubectl plugin
21
- Install ` px ` binary anywhere in your PATH and name it ` kubectl-px ` . You will
22
- then be able to run it like this:
23
-
24
- ```
25
- $ kubectl px get nodes
26
- $ kubectl px get pvc
27
- ```
28
-
29
20
## Creating a context
30
21
You can create a context using the following command:
31
22
@@ -37,6 +28,11 @@ See `px context create --help` for more information like setting the Kubeconfig.
37
28
38
29
> NOTE: The default gRPC SDK port for Portworx is 9020
39
30
31
+ ### Connecting to Portworx running on a Kuberentes Cloud
32
+ If you are running Portworx installed on a Kubernetes Cloud like GKE, EKS, etc,
33
+ you may need to use the workaround in issue #40 to access the Portworx gRPC
34
+ endpoint through the Kubernetes API.
35
+
40
36
### What if you don't have a Portworx cluster?
41
37
` px ` uses the [ OpenStorage SDK] ( https://libopenstorage.github.io ) to communicate
42
38
with Portworx, therefore it is fully compatible with OpenStorage's
@@ -48,11 +44,20 @@ $ docker run --rm --name sdk -d -p 9100:9100 -p 9110:9110 openstorage/mock-sdk-s
48
44
$ px context create --name=mycluster --endpoint=localhost:9100
49
45
```
50
46
51
- ## Status
47
+ ## Installing as a kubectl plugin
48
+ Install ` px ` binary anywhere in your PATH and name it ` kubectl-px ` . You will
49
+ then be able to run it like this:
50
+
51
+ ```
52
+ $ kubectl px get nodes
53
+ $ kubectl px get pvc
54
+ ```
55
+
56
+ ## px sample commands
52
57
Now that ` px ` has been setup with a context, you can do the following commands:
53
58
54
59
```
55
- $ px status
60
+ $ px describe cluster
56
61
$ px get volume
57
62
$ px get volume -o wide
58
63
$ px get nodes
0 commit comments