This feature will enable SWIFT to provision DR cluster dynamically during failover of DR policy of Stage1 type.


This policy that allows failover as well as fallback operations.


The policy defines rules and triggers for automatically provisioning new clusters. This can be based on workload demands, specific events, or schedules.


To enable dynamic provisioning for Stage1-only, you need to follow the steps mentioned below.


  1. You need to create a Stage-1 DR Policy. Then Select that policy and click on ‘Apply’ button and choose ‘Application Replication with DR cluster’. Please see below snippet.


  1. After that you will appear one window to provide the Stage1 replication and DR Cluster config.
  2. In the Stage1 Replication either you can choose new replication or existing, choose platform type as per your environment. And choose the cluster name, storage pool and so on.
  3. At DR Cluster Config: Basically, SWIFT does supports multiple clouds for dynamical DR cluster such as AWS, GCP, Azure, OCI and IBM. You can choose any one of these as per your requirements.
  4. Then provide cluster, namespace name that will create a automatically when your cluster provisioned.
  5. Storage class: If you left blank or if specified storageclass does not exists, then SWIFT will be used default storage class. 
  6. Version: We currently support versions 1.24 to 1.28, with plans to add more in the future as per Kubernetes releases.
  7. Node Count: Put the node count as per your requirements.
  8. Fallback Configuration: Choose zone.
  9. TRAIPOD Options: Configure as per your requirements. Refer TRAIPOD KB article for more information.
  10. AWS Configuration: Since you have selected AWS cloud in the DR cluster configuration, you should enter the AWS-related details, such as the Access Key, Region, Availability Zones (at least two), Instance Type, and Secret Key.
  11. Then, click ‘Apply.’
  12. If you want to make some customizations during this process, you can use the ‘advanced options. For more information, refer to the Advanced Options KB article.






  • Similarly, if you select GCP in DR cluster config. Then you should enter region, zone, upload the private key and then Apply to create GCP Dynamic DR cluster.



  • Same for Azure, then you need to provide below details:
    1. Subscription ID
    2. Tenant ID
    3. Client ID
    4. Resource Group (This is an Optional)
    5. Region
    6. Pricing tier
    7. Network config
    8. Node Size
    9. Client secret
  • If you select OCI,
    1. User ID
    2. Compartment Name
    3. Tenant ID
    4. API Key’s Fingerprint
    5. Region
    6. Availability domain (Optional)
    7. Network type
    8. Node Shape
    9. DR Cluster tag
    10. Private key file
  • If you select IBM,
    1. If you choose IBM VPC you need to enter below details
      • Metro
      • Zone
      • Resource group
      • Flavor
      • API key
    2. If you choose IBM Classic
      • Metro
      • Zone
      • Resource group
      • Flavor
      • API key