restgay.blogg.se - Turn off bypass checksum multipatch

Portworx supports using BackupLocation CR with IAM policy as an AWS s3 target for cloudsnaps triggered through Stork using ApplicationBackup CR. You can now deploy Portworx in IPv6 networking enabled environments.

This key can be used on any cluster to activate the license, provided you can report usage collected by the metering module.

You can enable pay-as-you-go billing for an air-gapped cluster with no outbound connectivity by acquiring a pay-as-you-go account key from Portworx.

Portworx will use the IBM CSI provider to automatically provision and manage its own storage disks.

You can now use Portworx with IBM cloud drives on VPC Gen2 infrastructure.

The CSI topology feature allows users of FlashArray Direct Access volumes and FlashBlade Direct Access filesystems to direct their applications to provision storage on a FlashArray Direct Access volume or FlashBlade Direct Access filesystem that is in the same set of Kubernetes nodes where the application pod is located.

On-premises users who want to use Pure Storage FlashArray with Portworx on Kubernetes can provision and attach FlashArray LUNs as a Direct Access volume.

Portworx by Pure Storage is proud to introduce the following new features: This functionality is only enabled after a system reboot.

Resolution: Portworx now avoids the deadlock by preventing access to the volume until attach is complete. This is because a system-generated IO can occur on the volume while the volume attach is in progress, causing the volume attach to wait for IO completion, which in turn waits for startup to complete, resulting in a deadlock. On certain kernel versions (5.4.x and later) during startup, volume attach sometimes got stuck, preventing Portworx from starting. Resolution: You can now add new nodes to the cluster. When a cluster is configured with PX-Security and using Floating license, it was not possible to add new nodes to the Portworx cluster. Resolution: When you restart Portworx now, it ensures that the mount path is deleted. This caused pods to be stuck in the terminating state. The mount path was not erased if you restarted Portworx at the wrong time during an unmount operation when using CSI. Workaround: Disabled the call home service on Portworx nodes by running pxctl sv call-home disable. The billing agent might try to reach outside the network portal in air-gapped environments. Resolution: The air-gapped bootstrap script has been updated and now includes the Grafana image. Customers using Prometheus monitoring needed to manually copy the Grafana container image into their environments. The Grafana image was not included into the list of images for the air-gapped bootstrap script. Resolution: Backups are now encrypted in this case. This encryption key, if set, is applied only to cloudsnaps irrespective of encrypted volumes.) (Note that this should not be confused with encrypted volumes. Pxctl status now shows a deprecation warning when internal objectstore is running on a cluster.īackups were not encrypted if BackupLocation in Kubernetes had an encryption key set for cloudsnaps. Portworx has upgraded or enhanced functionality in the following areas: Improvement Number

Starting with Portworx version 2.12.0, internal objectstore will be deprecated.