Which Portworx CRD object is used to set up essential parameters for a Portworx installation?

The StorageCluster is the primary Custom Resource Definition (CRD) used by the Portworx Operator to deploy and manage a Portworx cluster. This object's specification (spec) contains all the essential parameters for the installation, including the Portworx image version, storage device configurations, network interfaces, environment variables, and other cluster-wide settings. Administrators define the desired state of the Portworx installation within this single CRD object, and the Operator works to reconcile the cluster to match this state.

A. VolumeSnapshot: This is a standard Kubernetes API resource for creating point-in-time snapshots of persistent volumes. It is an operational object, not one used for configuring the Portworx cluster installation.

C. ServiceAccount: This is a standard Kubernetes object that provides an identity for processes running in pods. While Portworx uses ServiceAccounts for permissions, it is not the CRD for defining installation parameters.

1. Portworx Enterprise Documentation

"Portworx Spec CRD": "The StorageCluster custom resource is the main custom resource that you will interact with to deploy and manage the Portworx cluster. The Portworx Operator will watch for this custom resource and will deploy/update/delete the Portworx cluster based on the spec." (Reference found under the "Reference -> Portworx CRDs -> Portworx Spec CRD" section).

2. Portworx Enterprise Documentation

"Generate the Portworx spec": "The Portworx Operator deploys Portworx on your cluster using a spec from a StorageCluster object. You can generate this spec using the Portworx spec generator page in Portworx Central." (Reference found under the "Install and Configure -> Portworx on Kubernetes -> Install with the Operator -> On-premises" section).

3. Portworx Enterprise Documentation

"CRD-based configuration": This section details the various fields within the StorageCluster spec

such as image

storage

network

and env

confirming it is the central point for installation configuration. (Reference found under "Operate and Maintain -> Configuration -> CRD-based configuration").