Configure storage

​

Persistent storage volumes

​

Local PVs and storage classes

1. Preallocate local storage in each cluster node. The example creates five Solid State Drive (SSD) and Hybrid Hard Drive (HDDs) volumes respectively.

#!/bin/bash
for i in $(seq 1 5); do
  mkdir -p /mnt/ssd-bind/vol${i}
  mkdir -p /mnt/ssd/vol${i}
  mount --bind /mnt/ssd-bind/vol${i} /mnt/ssd/vol${i}
done
for i in $(seq 1 5); do
  mkdir -p /mnt/hdd-bind/vol${i}
  mkdir -p /mnt/hdd/vol${i}
  mount --bind /mnt/hdd-bind/vol${i} /mnt/hdd/vol${i}
done

2. Install the local volume provisioner.

kubectl apply -f /path/to/local-volume-provisioner/file.yaml

3. Verify that the local volume provisioner is created successfully.
   Copy

   Ask AI

   kubectl get po -n <k8s_namespace> |grep local-volume
   

4. Verify that all PVs are created successfully.
   Copy

   Ask AI

   kubectl get pv
   

5. Verify that all storage classes are created successfully.
   Copy

   Ask AI

   kubectl get storageclasses
   

​

Kubernetes default StorageClass

kubectl get sc

• volumeBindingMode: WaitForFirstConsumer
• reclaimPolicy: Retain
• allowVolumeExpansion: true (required field for the production deployments)

​

Multiple volumes

• Volume configurations for journals
  Copy

  Ask AI

  bookkeeper:
    volumes:
      # use a persistent volume or emptyDir
      persistence: true
      journal:
        # It determines the directory of journal data
        numVolumes: 1 # --- [1]
        numDirsPerVolume: 1 # --- [2]
  

  • [1] numVolumes: the number of volumes supported for each journal.
  • [2] numDirsPerVolume: the number of directories BookKeeper outputs its Write-Ahead Logs (WAL) to.
• Volume configurations for ledgers
  Copy

  Ask AI

  bookkeeper:
    volumes:
      # use a persistent volume or emptyDir
      persistence: true
      ledgers:
        name: ledgers
        size: 50Gi
        # It determines the directory of ledgers data
        numVolumes: 1 # --- [1]
        numDirsPerVolume: 1 # --- [2]
  

  • [1] numVolumes: the number of volumes supported for each ledger.
  • [2] numDirsPerVolume: the number of directories BookKeeper outputs ledger snapshots to.

​

Tiered Storage

• AWS S3
• Google Cloud Storage
• Azure Blob Storage

​

Enable Tiered Storage

​

Configure Tiered Storage for AWS S3

• Generate an AWS access key and secret access key.
• Create an AWS S3 bucket.
• Create a Kubernetes secret to save your AWS credentials with the command below. When you configure Tiered Storage, you can specify the Kubernetes secret. Pulsar brokers use the credentials stored in the Kubernetes secret to access the storage container. When your storage credentials change, you need to restart the Pulsar cluster.
  Copy

  Ask AI

  kubectl -n <k8s_namespace> create secret generic \
    --from-literal=AWS_ACCESS_KEY_ID=<aws_access_key> \
    --from-literal=AWS_SECRET_ACCESS_KEY=<aws_secret_key> \
    [secret name]
  

broker:
  offload:
    enabled: true
    managedLedgerMinLedgerRolloverTimeMinutes: ''
    managedLedgerMaxEntriesPerLedger: ''
    managedLedgerOffloadDriver: ''
    s3:
      enabled: true
      s3ManagedLedgerOffloadRegion: '[YOUR REGION OF S3]'
      s3ManagedLedgerOffloadBucket: '[YOUR BUCKET OF S3]'
      s3ManagedLedgerOffloadMaxBlockSizeInBytes: ''
      s3ManagedLedgerOffloadReadBufferSizeInBytes: ''
      s3ManagedLedgerOffloadServiceEndpoint: ''
      secret: '[the name of the created Kubernetes secret]'

​

Configure Tiered Storage for Google GCS

• Create a GCS service account.
• Create a GCS bucket.
• Create a Kubernetes secret to save your Google credentials with the following command. When you configure Tiered Storage, you can specify the Kubernetes secret. Pulsar brokers use the credentials stored in the Kubernetes secret to access the storage container. When your storage credentials change, you need to restart the Pulsar cluster.
  Copy

  Ask AI

  kubectl -n <k8s_namespace> create secret generic \
    --from-file=<gcs_service_account_path> \
    [secret name]
  

broker:
  offload:
    enabled: true
    managedLedgerMinLedgerRolloverTimeMinutes: ''
    managedLedgerMaxEntriesPerLedger: ''
    managedLedgerOffloadDriver:
    gcs:
      enabled: true
      gcsManagedLedgerOffloadRegion: '[YOUR REGION OF GCS]'
      gcsManagedLedgerOffloadBucket: '[YOUR BUCKET OF GCS]'
      gcsManagedLedgerOffloadMaxBlockSizeInBytes: ''
      gcsManagedLedgerOffloadReadBufferSizeInBytes: ''
      secret: '[the name of the created Kubernetes secret]'

​

Configure Tiered Storage for Azure Blob Storage

• Create an Azure storage account and a storage account access key.
• Create an Azure Blob container.
• Create a Kubernetes secret to save your Azure credentials with the command below. When you configure Tiered Storage, you can specify the Kubernetes secret. Pulsar brokers use the credentials stored in the Kubernetes secret to access the storage container. When your storage credentials change, you need to restart the Pulsar cluster.
  Copy

  Ask AI

  kubectl -n <k8s_namespace> create secret generic \
    --from-literal=AZURE_STORAGE_ACCOUNT=<azure_storage_account> \
    --from-literal=AZURE_STORAGE_ACCESS_KEY=<azure_storage_access_key> \
    [secret name]
  

broker:
  offload:
    enabled: true
    managedLedgerMinLedgerRolloverTimeMinutes: ''
    managedLedgerMaxEntriesPerLedger: ''
    managedLedgerOffloadDriver:
    azureblob:
      enabled: true
      managedLedgerOffloadBucket: '[YOUR BLOB CONTAINER]'
      managedLedgerOffloadMaxBlockSizeInBytes: ''
      managedLedgerOffloadReadBufferSizeInBytes: ''
      managedLedgerOffloadServiceEndpoint: ''
      secret: '[the name of the created Kubernetes secret]'