Astra Data Store preview requirements

Contributors netapp-mwallis netapp-dbagwell amgrissino

Get started by verifying that your environment meets Astra Data Store preview requirements.

Astra Data Store preview supports both bare-metal and VM-based deployments. Astra Data Store preview cluster can run on a Kubernetes cluster with four or more worker nodes. Astra Data Store preview software can co-exist with other applications running on the same Kubernetes cluster.

Astra Data Store preview only supports provisioning of PVs for Kubernetes workloads using the Astra Trident CSI driver. VM workloads will be supported in a future release of Astra Data Store.

Note If you plan to manage your Astra Data Store preview cluster from Astra Control Center, make sure your Astra Data Store preview cluster meets the requirements for clusters that will be managed by Astra Control Center in addition to the requirements outlined here.

Kubernetes worker node resource requirements

These are the minimum resource requirements required to be assigned to the Astra Data Store preview software on each worker node in the Kubernetes cluster:

Resource Minimum Maximum

Number of data drives

  • 3 (with a separate cache device present)

  • 4 (if there is no cache device present)

14

Data drive size

100GiB

4TiB

Number of optional cache devices

1 (8GiB or greater in size)

N/A

Number of vCPUs

10

10

RAM

35GiB

35GiB

Note For the best write performance, you should configure a dedicated high-endurance, low-latency, low-capacity cache device.

Each worker node has the following additional requirements:

  • 100GiB or greater free space on host disk (boot) for Astra Data Store preview log files to be stored.

  • At least one 10GbE or faster network interface for cluster, data, and management traffic. Optionally, an additional 1GbE or faster interface can be used to separate out management traffic.

Hardware and software requirements

Astra Data Store preview software is validated on the following hardware platforms, software, and storage configuration. Visit NetApp community support if your Kubernetes cluster configuration is different.

Hardware platforms
  • HPE DL360

  • HPE DL380

  • Dell R640

  • Dell R740

Storage

Astra Data Store preview has been validated with the following drive types:

  • Bare-metal deployments: Astra Data Store preview installed on a Kubernetes cluster directly on a Linux cluster without any hypervisor.

    • SATA or NVMe TLC SSDs.

  • VM-based deployments: Astra Data Store preview installed on a Kubernetes cluster on Linux VMs hosted on an ESXi cluster.

    • SATA, SAS, or NVMe TLC SSD-based datastores.

    • Drives presented as virtual disks or passthrough drives.

Note If your host uses SSDs behind a hardware RAID controller, configure the hardware RAID controller to use "passthrough" mode.
Note Each drive should have a unique serial number. Add the attribute disk.enableuuid=TRUE in the virtual machine advanced settings during VM creation.
Software
  • Hypervisor: Astra Data Store preview is validated with VMware-based VM deployments with ESXi 7.0. KVM-based deployments are not supported by Astra Data Store preview.

  • Astra Data Store preview has been validated on the following host operating systems:

    • Red Hat Enterprise Linux 8.4

    • Red Hat Enterprise Linux 8.2

    • Red Hat Enterprise Linux 7.9

    • Red Hat Enterprise Linux CoreOS (RHCOS)

    • CentOS 8

    • Ubuntu 20.04

  • Astra Data Store preview has been validated with the following Kubernetes distributions:

    • Red Hat OpenShift 4.7

    • Google Anthos 1.7

    • Kubernetes 1.21

    • Kubernetes 1.20

Note Astra Data Store preview requires Astra Trident version 21.10.1 for storage provisioning and orchestration. See the Astra Trident installation instructions.

Networking requirements

Astra Data Store preview requires one (1) IP address per cluster for MVIP. It needs to be an unused or unconfigured IP address in same subnet as MIP. The Astra Data Store preview management interface should be same as the Kubernetes node’s management interface.

In addition, each node can be configured as described in the following table:

Note The following abbreviations are used in this table:
MIP: Management IP address
CIP: Cluster IP address
MVIP: Management virtual IP address
Configuration IP addresses needed

One network interface per node

  • Two (2) per node:

    • MIP/CIP: One (1) pre-configured IP address on management interface per node

    • Data IP: One (1) unused or unconfigured IP address per node in same subnet as MIP

Two network interfaces per node

  • Three (3) per node:

    • MIP: One (1) pre-configured IP address on management interface per node

    • CIP: One (1) pre-configured IP address on data interface per node in a different subnet from MIP

    • Data IP: One (1) unused or unconfigured IP address per node in same subnet as CIP

Note You should omit the data network gateway field in the cluster Custom Resource (CR) file, astradscluster.yaml, for both of these configurations. The existing routing configuration on each node accommodates all of the addresses.
Note No VLAN tags are used in these configurations.

CSI driver

Astra Data Store preview requires the application Kubernetes clusters to be running Astra Trident 21.10.1. Astra Data Store preview can be configured as a storage backend with Astra Trident to provision persistent volumes.

CNI configuration

Astra Data Store preview has been validated with the following CNIs:

  • Calico and Weave Net CNIs for vanilla Kubernetes clusters

  • OpenShift SDN for Red Hat OpenShift Container Platform (OCP)

  • Cilium for Google Anthos

These CNIs require the host firewall (firewalld) to be disabled.

Persistent volume sharing requirements

Each Astra Data Store preview cluster supports using persistent volumes to address the storage needs of any apps installed on that cluster. Consider the following requirements for persistent volumes in Astra Data Store preview:

Requirements
  • The NFSv4.1 client/server must be installed on Kubernetes clusters.

  • The nfs-utils package must be installed on worker nodes.

  • Kubernetes apps access files using persistent volumes shared over NFSv4.1, which requires the AUTH_SYS authentication method.

Licensing

Astra Data Store preview requires an Astra Data Store preview license for full functionality. Sign up here to obtain the Astra Data Store preview license. Instructions to download the license will be sent to you after you sign up.

AutoSupport configuration

Astra Data Store preview requires AutoSupport to be enabled and have connectivity to the AutoSupport backend. This may be through direct internet access or proxy configuration.

The periodic settings that are used for sending mandatory telemetry AutoSupport bundles should not be changed. If you disable the sending of periodic AutoSupport bundles, the cluster will be locked down and new volumes cannot be created until periodic settings are enabled again.

What’s next

View the quick start overview.