Watch this short video that shows how to package your code in a Docker image and deploy:
Deployment is a three-step process.
- Create a Host (VM)
- Deploy the service (Application)
- Expose the application using LB
Create a host #
From the menu DevOps > Hosts > EC2 > +Add button above the table. Choose the desired instance type. The available instance types are set by your administrator or the plan you choose in DuploCloud. If you are not using this host for hosting containers, then set the pool as none. If you want a public IP for the host, then select the public subnet in the list of availability zones.
Deploy the service (application) #
From the menu DevOps > Containers > EKS/Native > +Add sign above the table. Give a name for your services (no spaces); number of replicas; Docker image; volumes (if any). The number of replicas must be less than or equal to the number of hosts in the fleet.
Expose the application using LB #
Create an ELB from the menu DevOps > Containers > EKS/ Native Select the desired service from the table and click on Load Balancer tab for Configuration. The URL suffix you specify under Health Check will be used by DuploCloud during a rolling upgrade i.e., when a service image is changed, then DuploCloud will take down one container replica at a time and bring up a new one. Once it’s running, then the DuploCloud agent running on the host will make a call to the URL and expects a 200 OK. If it does not get a 200 OK, then the upgrade is paused and the user needs to update with an image that fixes the issue.
- The DNS name for the service will be present in the Services Table. It takes about 5 to 10 minutes for the DNS name to start resolving.
- Update a Service from the menu DevOps > Containers > EKS/Native click on Edit button under Actions column of the Services table or Select the desired service from the table and click on edit option under the Actions menu button.