Launch a Deployment Template
Steps to launch a Deployment Template
1. In the left navigation panel, Click on Deployment Template.
2. Select the Deployment Template to be launched and click Launch.
Fill the details in the Launch Wizard to launch an application.
Step 1: Cluster and Deployment Template Version
Choose the Deployment Version and a Running cluster where the template needs to be launched.
Step 2: Volume Provision Policy
Select the Volume Type [Static or Dynamic]. In case of Dynamic Volume Type, choose the Volume Provision Policy. In case of Static Volume Type, select a pre-existing Volume.
In order to share a Dynamic Volume across multiple services, choose a provision policy of type 'Shared Volume'. For more information on Shared Volumes, check the documentation on 'Creating Shared Volumes across Services'
a) Dynamic Volume Type: Volumes are dynamically provisioned at the time of application launch. The Volume Provision Policy declares the configurations for provisioning a dynamic volume.
NOTE: Availability Zone in the Provision policy must match one of the cluster zones.
Select a Volume Provision Policy. If the Volume Provision Policy is configured to Retain the volumes, those dynamic volumes will be retained even after the application is deleted. These volumes can be viewed under the Infrastructure -> Volumes section.
b) Static Volume Type:
When a Static volume type is chosen, a pre-existing Released Volume in the same cluster can be reused at the time of launch. Static Volumes retain the data across application launches.
For eg. A template sampletemplate is launched on a samplecluster with Dynamic Volume Type and Retain configuration. This provisions a volume with id pvc-ac7e30bc-3ba7-4c7f-ae2c-f61773bbda01. Application is then deleted. The dynamically provisioned volume pvc-ac7e30bc-3ba7-4c7f-ae2c-f61773bbda01 moves to Released state. Launch the template sampletemplate on the samplecluster and choose Static Volume Type and select the Released Volume pvc-ac7e30bc-3ba7-4c7f-ae2c-f61773bbda01.
Step 3: Use Ingress ?
Check the different types of service access detailed here under Accessing a Service section. If Ingress is used, and if the Containers have route paths, each route path can be configured against a Domain Name. The Services can be accessed using the Domain Names on ports 80 and 443.
Step 3.1: Use Ingress
Note on Custom Ingress : If the Deployment Template has a Service of type 'Ingress', then the custom Ingress service will be deployed instead of the default ingress controller deployed by gopaddle.
Step 3.2: Do not use Ingress (Use Node Port)
If Ingress is not used, then each Container port needs to be mapped to a Cluster Node Port in the range 30000 - 30275. The Service can be access using a Node IP and the port mapped.
Step 4: Use LoadBalancer ?
Choose whether LoadBalancer is required.
Step 4.1: Ingress with LoadBalancer
If Ingress with LoadBalancer is required, then you can map the domain names to each route path in the container in step 5.
Step 4.2: Ingress without LoadBalancer
If Ingress without Load Balancer is chosen, then the HTTP and HTTPS ports in the Ingress can be mapped to alternate Node Ports.
If LoadBalancer is not chosen, then route paths cannot be mapped to specific Domain Names.
Step 4.3: Ingress Annotations
Add specific annotations to the Ingress deployment.
Step 5: Routes
Select Domains and Sub-domains for each route path in the Deployment Template.
Step 6: Domain SSL
Specify whether TLS certificate and Sticky Session to be enabled for each Domain.
Check the documentation on Sticky Session and Cookie settings here. If custom configurations are required, these can be overridden using the Ingress Annotations in step 4.3.
Step 7: ENV
Edit the default values for Environment Variables in Containers. This step is optional.
Step 8: Config
Edit the default Configurations and their Versions in Containers. This step is optional.
Step 9: Node Selector
If you desire to deploy specific services on specific nodes in the cluster, enable the Set Node Selector ? option. Upon selection, you can choose one or more values for each of the Node Label Keys. The available values are consolidated based on labels configured for all nodes in the cluster. When a Key/Value is set for a service, the service gets deployed on a node whose label satisfies the Key/Value selected. For more information on Node Selected, check the documentation here.
Step 10: Node Affinity
Choose the node affinity rules to decide the placement of the services. For more information on Node Affinity, check the documentation here.
3. Click on Launch to launch the application.