This page guides you to enable the RBAC functionality of PX-Security on an existing Kubernetes cluster. If you are installing a new cluster via the recommended Portworx Operator, see enable security in Portworx.
Enable RBAC an existing cluster
If you already have a working Portworx cluster and wish to enhance security by enabling RBAC, you will need to enable it for the entire Portworx cluster. Depending on how the cluster was installed, follow the steps for either the Operator-based installation or the (legacy) DaemonSet-based installation.
(Optionally) Generate a new cluster token.
If you use Disaster Recovery functionality or are using data-migrating functionality between Kubernetes clusters, run the following command to generate a new cluster token after these operations, as the token will have changed that is used for for pairing and migrating your clusters:
pxctl cluster token reset
You will then need to update any other clusters' clusterpair objects with the new token.
Implications on pxctl
pxctl command will also be secured. As a result, you may need to perform extra steps to run
Security parameter overview
The following parameters are utilized and required by PX-Security. With the recommended Operator-based installation, these are automatically created for you, but they can be manually changed if needed. However, they must be manually created and provided if you are enabling PX-Security on a legacy DaemonSet-based installation.
Environment variables (DaemonSet-based installation only)
You do not need to be specify any of these parameters on an Operator-based installation.
|Yes||Shared secret used by Portworx to generate tokens for cluster communications|
|Yes, when using Stork||Share secret used by Stork to generate tokens to communicate with Portworx. The shared secret must match the value of |
|Optional||Self-generated token shared secret, if any|
For non-sensitive information, you can use command-line parameters with the following arguments:
|JSON Web Token issuer (e.g. openstorage.io). This is the token issuer for your self-signed tokens. It must match the |
|JSON Web Token RSA Public file path|
|JSON Web Token ECDS Public file path|
|Name of the claim in the token to be used as the unique ID of the user (|