What is the minimum kernel needed for Portworx?
Comprehensive and Detailed Explanation From Exact Extract:
Portworx requires a minimum Linux kernel version of 3.10 or greater to operate properly. This requirement stems from Portworx's dependencies on certain kernel features and modules that became standard from kernel version 3.10 onwards. The kernel version affects support for device-mapper, overlay filesystems, network stack enhancements, and other low-level capabilities essential for Portworx's block storage functionality and performance. Although newer kernels (like 4.15+) offer additional features and improvements, Portworx maintains compatibility back to 3.10 to support a wide range of enterprise Linux distributions such as RHEL, CentOS, and Ubuntu LTS releases. The official Portworx system requirements document explicitly states kernel 3.10 as the minimum supported version to ensure stability and compatibility in production environmentsPure Storage Portworx System Requirementssource.
Portworx uses secrets to authenticate Kubernetes to the Portworx system.
When using the shared authentication method, where is that secret stored?
Comprehensive and Detailed Explanation From Exact Extract:
When using shared authentication in Portworx, the Kubernetes secret that contains the authentication token or credentials is stored in the same namespace where the application requesting storage resides. This placement ensures that the application pods have access to the secret needed to authenticate to Portworx for volume provisioning and management. It enables a security boundary aligned with Kubernetes namespaces, restricting credentials to the scope of the application. Storing the secret in the default namespace or the Portworx installation namespace would be less secure or less flexible in multi-tenant clusters. Portworx authentication documentation highlights this design for efficient, secure access management in Kubernetes environmentsPure Storage Portworx Security Guidesource.
What is the primary function of the telemetry pod added to each node when telemetry is enabled in Portworx?
Comprehensive and Detailed Explanation From Exact Extract:
When telemetry is enabled, Portworx deploys a telemetry pod on each node whose primary function is to collect diagnostic and performance data and securely upload it to Pure1, Pure Storage's cloud-based management and analytics platform. This pod gathers metrics such as resource utilization, error rates, and configuration changes, enabling proactive monitoring and predictive analytics. The data helps Pure1 provide customers with actionable insights, alerting, and automated support features, improving cluster reliability and reducing operational overhead. The telemetry pod does not directly monitor node health (which is the role of other components) nor manage network settings; its focus is on data collection and communication with Pure1. Official Portworx telemetry documentation highlights this pod as critical for enabling cloud-based health monitoring and customer support enhancementsPure Storage Portworx Telemetry Guidesource.
A Portworx administrator wants to create a storage class that can be used to create volumes with the following characteristics:
* Encrypted volume
* Two replicas
Which definition should the administrator use?
Comprehensive and Detailed Explanation From Exact Extract:
To create a StorageClass in Kubernetes for Portworx volumes that are encrypted and replicated twice, the correct parameters are encrypted: 'true' to enable encryption and repl: '2' to specify two replicas. Option A accurately sets these parameters, ensuring volumes provisioned with this StorageClass will be encrypted at rest and maintain two replicas for data redundancy. Option B uses sharedv4: 'true', which relates to NFS-like sharing, not encryption. Option C uses secure: 'true', which is not the recognized parameter for enabling encryption in Portworx StorageClass definitions. The official Portworx StorageClass parameter documentation confirms encrypted as the correct flag for encryption and repl to specify replication factor, enabling administrators to enforce data security and availability policies declaratively through Kubernetes manifestsPure Storage Portworx StorageClass Guidesource.
Which Portworx CRD object is used to set up essential parameters for a Portworx installation?
Comprehensive and Detailed Explanation From Exact Extract:
The StorageCluster Custom Resource Definition (CRD) is the central object used to configure and manage a Portworx installation on Kubernetes. It contains essential parameters including cluster-wide settings, KVDB configuration, storage pool definitions, security options, and CSI driver configurations. The StorageCluster resource declaratively defines how Portworx should be deployed, upgraded, and operated within the Kubernetes cluster. Administrators edit this object to adjust configurations, enabling features like telemetry, monitoring, and cloud integration. Unlike VolumeSnapshot (which manages snapshots) or ServiceAccount (which controls Kubernetes permissions), StorageCluster governs the overall lifecycle and parameters of the Portworx deployment. Portworx operator documentation identifies StorageCluster as the fundamental CRD for installation and configuration managementPure Storage Portworx Operator Guidesource.
Gary Martinez
6 days agoChristopher Phillips
26 days agoRachel Nelson
1 month agoBetty Lopez
2 months agoJustin Moore
2 months agoJeffrey Davis
3 months agoBrenda Phillips
2 months agoGerald Williams
2 months agoCharles Torres
3 months agoDorothy Hernandez
3 months agoBarbara Reed
2 months agoJesusita
3 months agoReita
4 months agoLaticia
4 months agoCharlette
4 months agoDorcas
4 months agoAn
5 months agoChara
5 months agoShawna
5 months agoSantos
5 months agoMyong
6 months agoVan
6 months agoBuddy
6 months agoZena
6 months agoShaniqua
7 months agoMargurite
7 months agoTarra
7 months agoElden
7 months agoCiara
8 months agoStephanie
8 months agoOzell
8 months agoMaile
8 months agoJerry
9 months agoJunita
9 months agoTresa
9 months agoDenny
9 months agoKiley
10 months agoMiriam
10 months agoMarvel
10 months agoKina
10 months agoBlythe
10 months agoMicaela
10 months ago