Normal Pulled 7m54s kubelet, k8s-node-2 Successfully pulled image "portworx/oci-monitor:2.5.0" Normal Pulling 7m55s kubelet, k8s-node-2 Pulling image "portworx/oci-monitor:2.5.0" Normal Scheduled 7m57s default-scheduler Successfully assigned kube-system/portworx-qxtw4 to k8s-node-2 Kubectl -n kube-system describe pods Events: Refer to the Cluster Topology awareness page for more details. You can also label nodes with custom labels to inform Portworx about region, zones and racks. Portworx automatically detects regions and zones that are populated using known Kubernetes node labels. Recommends using multiple availability zones when creating your VMware vSphere based cluster. Since Portworx is a storage overlay that automatically replicates your data, Portworx, Inc. Portworx will attach a set of 2 disks (one of size 200 and one of size 100) to each of the 4 storage nodes. Portworx will create a total of 8 disks (4 of size 200 and 4 of size 100).
Portworx will create a total 3 disks of size 200 each and attach one disk to each storage node. "-s", "type=zeroedthick,size=200", "-max_storage_nodes_per_zone", "1"įor a cluster of 6 nodes spanning 3 zones (zone-1a,zone-1b,zone-1c), in the above example Portworx will have 3 storage nodes (one in each zone) and 3 storage less nodes.When you scale up the cluster, the new nodes will also be storage nodes but while scaling down you will loose storage nodes causing Portworx to loose quorum. You can always ignore the max_storage_nodes_per_zone argument. While when you scale down the cluster, it will scale to the minimum size which ensures that all Portworx storage nodes are online and available. This ensures that when you scale up your cluster, only storage less nodes will be added. While planning capacity for your auto scaling cluster make sure the minimum size of your cluster is equal to the total number of storage nodes in Portworx.
The total number of storage nodes in your cluster will be Total Storage Nodes = (Num of Zones) * max_storage_nodes_per_zone. This instructs Portworx to limit the number of storage nodes in one zone to the value specified in max_storage_nodes_per_zone argument. You can specify the number of storage nodes in your cluster by setting the max_storage_nodes_per_zone input argument. Portworx allows you to create a heterogenous cluster where some of the nodes are storage nodes and rest of them are storageless. So in a failure event, if a new VM spins up, Portworx on the new VM will be able to attach to the same disk that was previously created by the node on the failed VM. Portworx tracks and manages the disks that it creates.End users can carve PVCs (Persistent Volume Claims), PVs (Persistent Volumes) and Snapshots from this storage cluster. Portworx will aggregate all of the disks and form a single storage cluster.Based on the given spec by the end user, Portworx on each node will create it’s disk on the configured shared datastore(s) or datastore cluster(s).Portworx runs on each Kubernetes minion/worker.Installation steps below are only supported if you are running with Kubernetes.īelow diagram gives an overview of the Portworx architecture on vSphere using shared datastores.