Design and Architecture Guide

Table of Contents:

• 1. Introduction
  • 1.1. Target Audience
• 2. Concepts and Definitions
  • 2.1. Kubernetes storage concepts
  • 2.2. Kubernetes compute concepts
  • 2.3. Connecting containers to storage
  • 2.4. Destroying and creating pods
  • 2.5. Container Storage Interface
• 3. NetApp Products and Integrations with Kubernetes
  • 3.1. Trident
  • 3.2. ONTAP
  • 3.3. Element OS
  • 3.4. SANtricity
  • 3.5. Azure NetApp Files
  • 3.6. Cloud Volumes Service for AWS
  • 3.7. Cloud Volumes Service for GCP
• 4. Kubernetes Cluster Architecture and Considerations
  • 4.1. Cluster concepts and components
  • 4.2. Cluster architectures
  • 4.3. Choosing an architecture
• 5. Storage for Kubernetes Infrastructure Services
  • 5.1. Persistent storage for cluster services
  • 5.2. Design choices and guidelines when using ONTAP
• 6. Storage Configuration for Trident
  • 6.1. Best practices for configuring ONTAP and Cloud Volumes ONTAP
  • 6.2. Best practices for configuring SolidFire
  • 6.3. Best practices for configuring E-Series
  • 6.4. Best practices for configuring Cloud Volumes Service on AWS
• 7. Deploying Trident
  • 7.1. Supported Kubernetes cluster architectures
  • 7.2. Trident installation modes
  • 7.3. Trident Installation on Docker UCP 3.1
  • 7.4. Deploying Trident as an enhanced CSI Provisioner
  • 7.5. CRDs for maintaining Trident’s state
  • 7.6. Trident Upgrade/Downgrade Process
  • 7.7. Recommendations for all deployments
  • 7.8. Deploying Trident to OpenShift
• 8. Integrating Trident
  • 8.1. Trident backend design
  • 8.2. Storage Class design
  • 8.3. Virtual Storage Pool Design
  • 8.4. PVC characteristics which affect storage provisioning
  • 8.5. Volume Operations
  • 8.6. Deploying OpenShift services using Trident
• 9. Backup and Disaster Recovery
  • 9.1. Backing Up Kubernetes and Trident’s state
  • 9.2. ONTAP Snapshots
  • 9.3. Data replication using ONTAP
  • 9.4. ElementOS snapshots
• 10. Security Recommendations
  • 10.1. Run Trident in its own namespace
  • 10.2. CHAP authentication