expand-storage-pool-index
As your cluster usage increases and the data on your storage pools grows, you may start to run out of capacity. In order to correct this, you must determine the most efficient way to expand your storage pool size.
Portworx allows you to expand your storage pools completely online (with a few exceptions) with the following two methods:
-
resize-drive: Using this method, you can vertically expand the storage pool size by increasing the size of the existing drives. All drives in the pool need to be resized to the same size for this operation. If the underlying infrastructure or the cloud provider supports resizing drives, this is the preferred option, as resizing disks involves no data movement and ensures zero downtime.
-
add-drive: Using this mode, you can horizontally expand the storage pool by adding drives. The new drive(s) will need to match the existing drives in size and IOPS properties (if available). This operation might involve a significant amount of data movement, since the existing data needs to be restriped. This operation can also be performed online and requires no downtime. Note that the pool runs in degraded mode during the
add-drive
operation.Limitations:
- If the pool is at or greater than 90% of its capacity, this operation can only be performed in pool maintenance mode.
If a pool to be resized contains an auto journal device, Portworx automatically performs data partition resizing as part of the expansion operation.
Expand storage pool sizeβ
Depending on the drives you want to use to expand a pool, proceed to one of the following sections:
ποΈ Post-installation
Ensuring Portworx is functional post installation
ποΈ Post-installation
Ensuring Portworx is functional post installation
ποΈ Post-installation
Ensuring Portworx is functional post installation
ποΈ alerts
| Name | ResourceType | Severity | Description | Metric |
ποΈ autopilot
6 items
ποΈ CloudUserRequirements
Create a custom role for Portworx
ποΈ cloud-drive-operations
4 items
ποΈ cloud-references-auto-disk-provisioning-asg-examples-aws
Examples:
ποΈ cloud-references-auto-disk-provisioning-asg-examples-gcp
Examples:
ποΈ cloud-references-auto-disk-provisioning-asg-examples-vsphere
Examples:
ποΈ cloud-references-auto-disk-provisioning-asg-limit-storage-nodes
Portworx allows you to create a heterogenous cluster where some of the nodes are storage nodes and rest of them are storageless.
ποΈ Portworx vSphere generic spec generation
Portworx vSphere generic spec generation
ποΈ Portworx vSphere generic spec generation
Portworx vSphere generic spec generation
ποΈ Portworx vSphere installation
Portworx vSphere installation
ποΈ Kubernetes secret for VMware
Kubernetes secret for VMware
ποΈ Portworx VMware shared architecture
Portworx VMware shared architecture
ποΈ Customize Security in Portworx
This document guides you through optionally customizing your Portworx Operator Security configuration further to fit specific needs.
ποΈ Enable security in Portworx
This document guides you through editing the Portworx manifest YAML file as shown in
ποΈ Enable security in Portworx
This document guides you through enabling PX-Security in your cluster by adding a single flag to your StorageCluster object.
ποΈ Example application
1. Create and apply the following pvc.yaml file:
ποΈ cloud-references-security-kubernetes-shared-secret-model-example-storageclass-operator-ocp
In the previous section, you created a StorageCluster in the `` namespace with security enabled.
ποΈ cloud-references-security-kubernetes-shared-secret-model-example-storageclass-operator
β
ποΈ Step 3: StorageClass Setup
In the previous section, you saved the Kubernetes token in a secret called px-user-token in the `` namespace. Now you can create a StorageClass which points Portworx to authenticate the request using the token in the that secret.
ποΈ Generate shared secrets
This guide uses a model based on shared secrets as the method to create and verify tokens. The goal is to store the shared secrets in a secure Kubernetes Secret object to then provide to Portworx.
ποΈ cloud-snaps-naming-scheme
Cloud backups adhere to the following naming scheme: /-.
ποΈ Shared Volumes
Explanation on Portworx Sharedv4 volumes to allow multiple containers access to one volume
ποΈ Configure migrations to use service accounts
Configure migrations to use service accounts
ποΈ Configure migrations to use service accounts
Configure migrations to use service accounts
ποΈ crd
1 item
ποΈ create-pure-flashblade
Use FlashBlade as a Direct Access filesystem
ποΈ create-pvc-access-via-non-root-users
This document describes how to access a Portworx Volume (PVC/PV) as a non-root user. By default, all the Persistent Volumes are accessible only by the root user. However, you can modify the application pod spec to allow a specific set of users to access the Persistent Volume as explained below.
ποΈ create-pvc-control-volume-provisioning
Portworx provisions volumes with little configuration from you. By default, Portworx thin provisions volumes and balances them according to current usage and load within the cluster.
ποΈ create-pvc-create-proxy-volume-pvcs
Portworx proxy volumes proxy an external data source onto a Portworx volume. The actual data for these volumes resides on the external data source and does not consume any storage from the Portworx storage pools.
ποΈ create-pvc-create-readonlymany-pvcs
This guide provides steps for mounting a disk in the ReadOnlyMany (ROX) access mode. The in-tree Portworx driver for Kubernetes does not support creating PVCs with the ReadOnlyMany access mode. To achieve this functionality, follow the steps below:
ποΈ create-pvc-create-sharedv4-pvcs
This document describes how to use Portworx sharedv4 (ReadWriteMany) volumes in your cluster.
ποΈ create-pvc-open-nfs-ports
SharedV4 volumes utilize NFS services, and they therefore require specific open NFS ports to allow for communication between nodes in your cluster. Depending on how your cluster nodes are configured, your firewall may block some of these ports, or your NFS ports may differ from the defaults. To solve these issues, you may need to manually assign NFS ports and ensure that your firewall or ACL allows them to communicate.
ποΈ create-pvc-pure-flasharray
On-premises users who want to use Pure Storage FlashArray with Portworx on Kubernetes can attach FlashArray as a Direct Access volume. Used in this way, Portworx directly provisions FlashArray volumes, maps them to a user PVC, and mounts them to pods. Once mounted, the application writes data directly onto FlashArray. As a result, this mounting method doesnβt use storage pools.
ποΈ create-pvc-px-fastpath-pvc
PX-Fast is a Portworx feature that enables an accelerated IO path for the volumes that meet certain prerequisites. It is optimized for workloads requiring consistent low latencies. PX-Fast is built on top of a Portworx PX-StoreV2 datastore.
ποΈ create-pvc-resize-pvc
This document describes how to dynamically resize a volume (PVC) using Kubernetes and Portworx.
ποΈ create-pvc-using-preprovisioned-volumes
This document describes how to use a pre-provisioned volume in your cluster.
ποΈ index
8 items
ποΈ Disaggregated installation
Learn how to install Portworx in disaggregated mode.
ποΈ disaster-recovery
15 items
ποΈ encryption shared docs
1 item
ποΈ expand-storage-pool-index
As your cluster usage increases and the data on your storage pools grows, you may start to run out of capacity. In order to correct this, you must determine the most efficient way to expand your storage pool size.
ποΈ expand-storage-pool-managed-by-px
If you're running on the cloud, consider automation into your decision for which pool resize approach you use. The pxctl service pool expand command allows you to perform resize operations without manually adding new drives or increasing drive capacity on your cluster.
ποΈ expand-storage-pool-not-managed-by-px
If you are running Portworx in an environment where you need or want to manually resize a pool using drives that are not managed by Portworx, then follow these steps:
ποΈ gce shared docs
2 items
ποΈ helm
4 items
ποΈ hidden
13 items
ποΈ ibm-uninstall-px
1. Edit your Portworx StorageCluster:
ποΈ Portworx command line arguments
Command line arguments to the Portworx daemon
ποΈ Reference for the Portworx config.json configuration file
Reference for the Portworx config.json configuration file
ποΈ Configure on Docker (shared)
Learn how to configure Porworx as a runC container
ποΈ Enable on Docker (shared)
Learn how to enable Porworx as a runC container
ποΈ Install on Docker (shared)
Learn how to install Porworx as a runC container
ποΈ Shared content for all AWS-KMS secret docs - cluster wide intro
Shared content for all AWS-KMS secret docs - cluster wide intro
ποΈ Shared content for all AWS-KMS secret docs - named secrets
Shared content for all AWS-KMS secret docs - named secrets
ποΈ key-management-aws-kms-px-secret-name-default
Take a note of the annotation px/secret-name: default. This specific annotation indicates Portworx to use the default secret to encrypt the volume. In this case, it will NOT create a new passphrase for this volume and NOT use per volume encryption. If the annotation is not provided then Portworx will use the per volume encryption workflow as described in the previous section.
ποΈ key-management-aws-kms-shared-px-secret-name-mysecret
Take a note of the annotation px/secret-name: mysecret. This specific annotation indicates Portworx to use the the secret called mysecret to encrypt the volume. In this case, it will NOT create a new passphrase for this volume and NOT use per volume encryption. If the annotation is not provided then Portworx will use the per volume encryption workflow as described in the previous section.
ποΈ Shared content for all AWS-KMS secret docs - secure flag
Shared content for all AWS-KMS secret docs - secure flag
ποΈ key-management-aws-kms-unique-passphrase
In this method, each volume will use its own unique passphrase for encryption. Portworx relies on the AWS KMS APIs to generate a Data Encryption Key. This key will then be used to encrypt and decrypt your volumes.
ποΈ Shared content for all AWS-KMS secret docs - warning note
Shared content for all AWS-KMS secret docs - warning note
ποΈ Shared content for all Kubernetes secrets docs - encrypted storage class spec
Shared content for all Kubernetes secret docs - encrypted storage class spec
ποΈ Shared content for all gcloud - named secrets
Shared content for all gcloud - named secrets
ποΈ Shared content for all Kubernetes secrets docs - intro
Shared content for all Kubernetes secret docs - intro
ποΈ Shared content for all Kubernetes secrets docs - encrypted storage class spec
Shared content for all Kubernetes secret docs - encrypted storage class spec
ποΈ Shared content for all Kubernetes secrets docs - per volume secret
Shared content for all Kubernetes secret docs - per volume secret
ποΈ Shared content for all Kubernetes secrets docs - set cluster-wide passphrase
Shared content for all Kubernetes secret docs - set cluster-wide passphrase
ποΈ Shared content for all Kubernetes secrets docs - set cluster-wide secret
Shared content for all Kubernetes secret docs - set cluster-wide secret
ποΈ Shared content for all Kubernetes secrets docs - shared secret warning note
Shared content for all Kubernetes secret docs - encrypted storage class spec
ποΈ Shared content for all Kubernetes secrets docs - storage class encryption
Shared content for all Kubernetes secret docs - storage class encryption
ποΈ Shared content for all Kubernetes secrets docs - storage class encryption
Shared content for all Kubernetes secret docs - storage class encryption
ποΈ Shared content for all Kubernetes secrets docs - volume cluster-wide secret
Shared content for all Kubernetes secret docs - volume cluster-wide secret
ποΈ OCP Network Prerequisites
Portworx network requirements
ποΈ Managing VM-Based Workloads in Kubernetes with KubeVirt and Portworx
This feature is under Directed Availability. Please engage with your Portworx representative if you are interested and need to enable it in your environment under the current guidelines.
ποΈ kvdb-for-portworx
3 items
ποΈ max-replication-factor
The maximum replication factor is 3.
ποΈ metrics
backup_stats stats
ποΈ migration
4 items
ποΈ migration-with-stork
The default admin namespace is kube-system. In all examples, `` is considered the admin namespace responsible for migrating all namespaces from your source cluster to the destination cluster. Alternatively, you can specify a non-admin namespace, in such a case, only that specific namespace will be migrated. To learn how to set up an admin namespace, refer to the Set up a Cluster Admin namespace for Migration page.
ποΈ monitor
2 items
ποΈ Install Portworx Operator on OpenShift
Install Portworx Operator on OpenShift with dynamic plugin
ποΈ OCP Network Prerequisites
Portworx network requirements
ποΈ Install Portworx on OpenShift version 4.12
Procedure for a fresh installation or upgrading Portworx from previous OpenShift versions.
ποΈ on-prem-pks-common-install
shared install for pks on-prem
ποΈ operation-tune-performance
In its default configuration, Portworx attempts to provide good performance across a wide range of situations. However, you can improve your storage performance on your environment by configuring a number of settings and leveraging features Portworx offers. To get the most out of Portworx, follow the guidance provided in this article.
ποΈ operations
9 items
ποΈ Shared content for install Portworx with Kubernetes - apply the specs
Shared content for install Portworx with Kubernetes - apply the specs
ποΈ configure gcloud shared content
configure gcloud shared content
ποΈ install operator
install operator
ποΈ Monitor operator shared content
monitor operator shared content
ποΈ Kubernetes disaster recovery Stop/Start the application on the source cluster
Kubernetes disaster recovery stop migration
ποΈ Shared content for install Portworx with Kubernetes - apply the specs
Shared content for install Portworx with Kubernetes - apply the specs
ποΈ Discussion forum
Link to the discussion forum
ποΈ Prepare AWS Kubernetes
Learn about preparing AWS Kubernetes.
ποΈ Shared content for GCP
Setup a production ready Portworx cluster Google Cloud Platform (GCP).
ποΈ Shared content for GCP
Setup a production ready Portworx cluster Google Cloud Platform (GCP).
ποΈ GCP service account
Setup a production ready Portworx cluster Google Cloud Platform (GCP).
ποΈ Shared
Generate and Apply a ClusterPair Spec
ποΈ Kubernetes disaster recovery and migration docs - migration common
Kubernetes disaster recovery and migration docs - migration common
ποΈ portworx-install-with-kubernetes-disaster-recovery-stork-helper
Always use the latest storkctl binary tool by downloading it from the current running Stork container.
ποΈ Shared
Shared content about Portworx installation in OpenShift
ποΈ Shared
Learn how to install Portworx with Kubenetes
ποΈ Shared
Shared content about Portworx installation in OpenShift
ποΈ Shared content for install Portworx with Kubernetes - post install
Shared content for install Portworx with Kubernetes - post install
ποΈ Shared content for install Portworx with Kubernetes - resize a Portworx PVC
Shared content for install Portworx with Kubernetes - resize a Portworx PVC
ποΈ Shared
Learn how to install Portworx with Kubenetes
ποΈ Shared
Learn how to install Portworx with Kubernetes
ποΈ Shared content for Kubernetes snapshots - restore PVC from snap
Shared content for Kubernetes snapshots - restore PVC from snap
ποΈ Volume options
Volume options
ποΈ px-wipe-airgapped
When wiping Portworx in Kubernetes, a number of docker images are fetched from registries on the internet. If your nodes don't have access to the public container registries on the internet, you can load these images onto your nodes yourself. Perform the steps below to wipe Portworx from an air-gapped cluster.
ποΈ Creating Snapshots
Learn how to create snapshots with pxctl
ποΈ Creating Snapshots- Intro
Learn how to create snapshots with pxctl- Intro
ποΈ Optimized Restores- Definition
Explains what is an optimized restore
ποΈ Restoring Volumes from Snapshots
Learn how to restore volumes from snapshots
ποΈ Shared content for managing snapshot schedule policies using pxctl
Shared content for managing snapshot schedule policies using pxctl
ποΈ Portworx Secrets- Definition
Explains what is a Portworx secret
ποΈ secure
4 items
ποΈ storage-operations
8 items
ποΈ troubleshooting
8 items
ποΈ uninstall-decomission-a-node
This guide describes a recommended workflow for decommissioning a Portworx node in your cluster.
ποΈ uninstall-portworx-ocp
1. Log in to the OpenShift console.
ποΈ uninstall-px-using-operator
Using the Portworx Operator, you can efficiently uninstall Portworx from your clusters. This can be achieved by updating the StorageCluster object, and you have the option to either keep the data on your drives or wipe them completely.
ποΈ upgrade
8 items
ποΈ vCenter server user privileges
Lists the VCenter minimum privileges for a user
ποΈ volume-placement-strategies-crd-reference
Portworx provides a CustomResouceDefinition (CRD) called VolumePlacementStrategy. The specification for this CRD is composed of 4 main sections: