An outline of DuploCloud's Stacks feature for replicating, customizing, and managing resources
DuploCloud's Stacks feature is a no-code/low-code solution for importing, replicating, and managing resources across cloud environments. DuploCloud Stacks empowers users to replicate resources quickly and easily, minimizing onboarding time and reducing reliance on niche expertise.
Stacks supports a variety of use cases, from importing resources from external cloud providers like AWS, GCP, or Azure into the initial DuploCloud environment to replicating resources within the DuploCloud Platform. It facilitates iterative imports, allows granular scope selection for resources, and supports both form-based and JSON-based edits to customize configurations.
Clone resources from one Tenant to another using the DuploCloud Stacks feature
Clone resources (Nodes, Hosts, Services, Secrets, storage, etc.) from one Tenant to another using DuploCloud Stacks.
Select the destination Tenant from the Tenant list box.
Navigate to Automation -> Stacks.
On the Deployments tab, click Clone. The Create Tenant Clone Job pane displays.
Provide a Name for the clone Tenant, select the source Tenant from the Source Tenant list box, and specify the resources to be cloned in the Scope field.
Click Next. The Deployment page for the clone job displays.
On the Deployment page, configure the clone job details:
Select or unselect the resources you want to include in the clone job.
Click the edit icon () beside a resource to open and edit its settings. Click Save to save your changes.
Click Submit. The selected resources from the source Tenant are cloned into the destination Tenant.
Create a re-usable template to deploy resources using the DuploCloud Stacks feature.
Create a re-usable template to deploy resources (Nodes, Hosts, Services, Secrets, storage, etc.) using the DuploCloud Stacks feature.
Select the Tenant from the Tenant list box that owns the resources that will act as a baseline for the new template.
Navigate to Automation -> Stacks.
Select the Templates tab.
Click Generate. The Generate Deployment Template pane displays.
Enter a name for the template in the Name field.
Select all applicable scopes in the Scopes field. If unsure, you can safely add any scope, as it only affects the resource lists shown on the next page. The following scopes are currently available, with more to be added as new resource types are supported:
Kubernetes
Admin / Reverse Proxy
Admin / System Config
Click Next. A page allowing you to edit the template configurations displays.
Edit the template configurations as needed:
The left panel displays resources and their components (e.g., Kubernetes, Service, and filebeat-k8s-duploinfrasvc) organized hierarchically.
Subcomponents can be toggled on or off, controlling their inclusion in the template.
Click the Download button to save the template file to your local machine for further use or modifications.
Admin / Tenant Security
Cloud / Host
Cloud / Load Balancer
Cloud / Storage
Docker
The right panel displays JSON that dynamically reflects the selections made on the left.
Adding or removing components on the left modifies the corresponding nodes and payloads in the JSON.
Advanced users can click Edit to fine-tune the JSON manually.
Click Save to save your changes.
Deploy resources to Tenants using templates with DuploCloud Stacks
Deploy resources (Nodes, Hosts, Services, Secrets, storage, etc.) to a Tenant using the DuploCloud Stacks feature.
Upload templates in advance to make them available for deployment across all Tenants or for a specific Tenant to make them available only within that Tenant's environment. You can upload a template for a specific Tenant ahead of time, or at the time of deployment.
From the DuploCloud Portal, navigate to Administrator -> System Settings.
Select the Templates tab.
Click Upload. The Upload Template pane displays.
Select the Tenant that will use the template from the Tenant list box.
Navigate to Automation -> Stacks.
Select the Templates tab, and click Upload. The Upload Template pane displays.
Enter a name for the template in the
While creating a deployment following the , select the Upload File option, and upload the template you wish to use for the deployment.
Access a read-only version of the template to view. To download an editable version of a template, see the .
From the DuploCloud Portal, navigate to Administrator -> System Settings.
Select the Templates tab.
In the row of the template you want to view, click the menu icon (), and select View.
Select the Tenant that will use the template from the Tenant list box.
Navigate to Automation -> Stacks.
In the row of the template you want to view, click the menu icon (), and select View.
From the DuploCloud Portal, navigate to Administrator -> System Settings.
Select the Templates tab.
In the row of the template you want to Download, click the menu icon (), and select Download.
Select the Tenant that will use the template from the Tenant list box.
Navigate to Automation -> Stacks.
In the row of the template you want to Download, click the menu icon (), and select Download.
From the DuploCloud Portal, navigate to Administrator -> System Settings.
Select the Templates tab.
In the row of the template you want to delete, click the menu icon (), and select Delete.
Select the Tenant that will use the template from the Tenant list box.
Navigate to Automation -> Stacks.
In the row of the template you want to delete, click the menu icon (), and select Delete.
Select the Tenant from the Tenant list box.
Navigate to Automation -> Stacks.
Select the Deployments tab.
Click Deploy. The Deploy Template pane displays.
View a deployment's logs or configurations (in JSON).
Select the Tenant from the Tenant list box.
Navigate to Automation -> Stacks.
Select the Deployments tab.
Click on the deployment you want to view in the NAME column. Details for the selected deployment display.
In the Module Type list box, Stack is selected by default. For steps related to the Agent Module Type, see below.
Click Choose File and select the file to upload.
Click Upload.
Click Choose File, and select the file to upload.
Click Upload.
Enter a deployment name in the Name field.
Select how you will provide a template:
Upload File: Click Choose File and select the file to upload.
Select Template: From the Deploy Template list box, select the template to deploy.
Click Next.
If a dialog box displays, enter values for any necessary input variables, and click Next.
Click Deploy. Resources from the selected template are deployed into the selected Tenant.
On the left is a list of Resources organized hierarchically. Select the resource(s) you want to investigate.
On the right, details for the selected resource(s) display. Select JSON or Logs to inspect specific configurations or logs for that resource.
Click Close to return to the Deployments tab.
Define custom input parameters and use built-in substitution keys to enhance Stacks deploy templates
These customization options are intended for advanced users familiar with JSON editing and deployment workflows. Improper modifications can break the template, potentially making it difficult to troubleshoot and restore. To avoid issues, always maintain a version history or backup of the original template before making changes. While some features, like adding custom input parameters, are straightforward and significantly enhance template utility, use caution when making complex edits.
For example, you can use a different instance size for a node.
Custom template input variables enhance template reusability by allowing dynamic values to be defined and inserted during use. To create a custom variable, wrap its name with double curly braces, like this: {{My Parameter Name}}. When the template is processed, you will be prompted to provide a value for each custom variable. This makes your templates more flexible and adaptable to different scenarios.
Substitution keys are predefined strings that are automatically replaced with corresponding values during template processing. Unlike custom template parameters, substitution keys do not require wrapping with special characters like double curly braces and are not listed in the pop-up dialog for custom input parameters. They can be inserted directly into the JSON template and will resolve dynamically. Below is a list of available built-in substitution keys and their descriptions.
You can remove a resource from a deployment template to exclude it permanently. While this functions the same as unchecking a resource in the tree displayed just before deployment, the key difference is that the resource will no longer appear in the list at all.
ref.duplo!dnssuffix
External DNS Suffix for the Tenant's Plan.
ref.duplo!tenantid
Tenant ID
ref.duplo!tenantname
Tenant name
ref.duplo!tenantinfraname
Infrastructure name
ref.duplo!tenantregion
Tenant region (e.g., us-east-1).
ref.duplo!k8sclustername
K8s cluster name (the cluster deployed under the Tenant's Plan).
ref.duplo!eksami
AWS AMI ID for the latest EKS Node Image compatible with the Tenant's cluster version.