Kubernetes pods, volumes, and projects

Cloud services on NetApp HCI involves pods, volumes, and projects that you create and manage by using NetApp Kubernetes Service (NKS). Persistent volumes are managed by Trident software.

Kubernetes pod
Each Kubernetes pod is a set of one or more containers. Pods run in several replicas of each service ensuring no single point of failure for critical services. In the Kubernetes architecture, a set of containers can be deployed and scaled together. This is achieved by using pods, which are the minimum unit of deployment in a Kubernetes cluster that enable more than one container to share the same resources, such as IP address and file systems.
Kubernetes project
A Kubernetes project is a construct for grouping applications, for example, Wordspace or MySQL. A project is a namespace with RBAC on the Kubernetes cluster.
Kubernetes volume
A Kubernetes volume is storage provisioned directly to a pod. NetApp Kubernetes Service supports a wide variety of volume types, including Amazon EBS, Azure Disk Storage, Google Persistent Disk, NFS, and many more. Volumes enable the containers within a pod to share information and are destroyed when their parent pod is deleted.
Persistent volume
With NKS, you can use a persistent volume, one that exists independently of any specific pod and with its own lifetime. Persistent volumes can be used to support stateful applications, such as database services, enabling all components of an enterprise solution to be deployed and managed by NKS. Using Trident to manage persistent volume claims (PVCs) insulates the developers creating pods from the lower-level implementation details of the storage that they are accessing.
Trident software
NKS on NetApp HCI employs Trident software to provision storage automatically to containerized applications. Trident is automatically deployed and configured when new NKS clusters are created. When a containerized application issues a PVC request, Trident dynamically provisions storage per the parameters requested against either the NetApp Element software storage layer in NetApp HCI directly or if available, the locally running Cloud Volumes service.