Deployments (Infrastructure)
The "Deployments" component in the Infrastructure section stands as the practical application of the Infrastructure Templates. It is here that the predefined templates are brought to life, initiating the actual process of provisioning and configuring the infrastructure resources as per the configuration set in the templates.
Deployments ensure that the resources are instantiated consistently, based on the parameters and configurations specified within the chosen template.
To simplify, while the Templates provide the blueprint, the Deployments actualize them, translating the theoretical configurations into real-world, operational infrastructure components.
Step 1 - Access the Deployments menu which can be found in the Infrastructure section. Here, you will be presented with a list showcasing all previously created deployments.
Step 2 - Initiate Deployment Creation: Locate and click the Create deployment button
Step 3 - Select Desired Template: Upon clicking, a dropdown list will appear containing available infrastructure templates. Browse through and select the template you wish to use for your new deployment. Click Create
Step 4 - Deployment Creation Page: After selecting the template, you will be redirected to the deployment creation page. This space is dedicated to customizing and setting the various arguments and configurations tied to your deployment. Here, you will be able to tailor various settings, parameters, and configurations based on the specifics of the chosen template.
Argument | Description |
|---|---|
TemplateName | Pre-populated based on your previous selection. |
Template id | Pre-populated based on your previous selection. |
Owner | Specify the owner responsible entity for this deployment |
Name | Specify the name of your deployment |
Description | A short description of the deployment |
Tags | Add a tag to your new deployment for easy reference |
Environment action | This argument allows adding business logic for the environments lifecycle, and can be defined through: -> Terminate - This is when the environment is terminated when the default timeand grace timereaches 0 seconds-> Manual - Manual trigge |
ETA | The default expiration time when the environment action is triggered. Select date from calendar. |
Grace time | The grace time to wait after the default time for the environment action to be triggered. |
Input variables | Variables are used to generate random data. You can use them in the values field of the extra arguments section. You can combine them with other values. For example, {{set_string}} - test the result will be a random string followed by the word test. You can also use them in a payload from a value of extra arguments, combined with other values or predefined variables. The following predefined variable categories are available: -> Infra -> User -> Function Additional parameters can also be added, the platform supporting various formats such as string, numeric, JSON, Code, List or Boolean |
Step 5 - Finalize Deployment: Once you've made all necessary customizations and reviewed your configurations for accuracy, Kubeark offers you two options, select the one that best suits your deployment needs.
Deploy & Plan
Deploy & Apply
