Skip to main content

AWS EBS CSI Driver

Overview​

AWS EBS CSI Driver is available as an add-on within Ankra's platform, allowing you to automatically manage AWS Elastic Block Store (EBS) volumes for your containerized workloads in Kubernetes. With Ankra, the AWS EBS CSI Driver can be easily deployed and configured in your clusters with minimal manual intervention.

Configuration Options​

The AWS EBS CSI Driver add-on offers configurable inputs to customize the deployment based on your cluster's requirements. Here are the available inputs:

Inputs​

  • Helm Chart Version
    This input sets the version of the AWS EBS CSI Helm chart to deploy.

    • Default: 2.25.0
    • Options:
      • 2.25.0 (default)

    Example:

    helm_chart_version: "2.25.0"

  • Service Monitor Enabled
    This option controls whether the Prometheus service monitor is enabled for AWS EBS CSI Driver. If you have Prometheus installed (requires the Prometheus add-on), you can enable this to monitor the health and performance of the AWS EBS CSI Driver.

    • Default: true
    • Options:
      • true (default)
      • false

    Example:

    service_monitor_enabled: "true"

Credentials​

The kubernetes nodes created by Ankra, while agnostic, are integrated with the cloud provider IAM. No credentials required during the setup.

Usage​

Deploying AWS EBS CSI Driver​

To deploy the AWS EBS CSI Driver in your Kubernetes cluster using Ankra, follow these steps:

  1. Access the Add-ons Section
    In Ankra's platform, go to the Add-ons section and select AWS EBS CSI Driver from the list of available add-ons.

  2. Configure Inputs
    You will be prompted to configure the available inputs for the add-on:

    • Helm Chart Version: Choose the required version or leave it as the default.
    • Service Monitor Enabled: If you are using Prometheus for monitoring, you can enable this option to track the health and performance of the EBS CSI Driver.

    Example configuration:

    helm_chart_version: "2.25.0"
    service_monitor_enabled: "true"

  3. Use AWS EBS Controller

    apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
    name: ebs-pvc
    spec:
    accessModes:
        - ReadWriteOnce
    resources:
        requests:
        storage: 20Gi
    storageClassName: ebs-sc  # Reference the custom EBS StorageClass