Step 9: Test the Application

Test the application to ensure you get the results you expect

You can test your application directly from the Services page using the DNS status card.

Estimated time to complete Step 9 and finish tutorial: 10 minutes.

Prerequisites

Before testing your application, verify that you accomplished the tasks in the previous tutorial steps. Using the DuploCloud Portal, confirm that:

• An Infrastructure and Plan exist, both named NONPROD.

• The NONPROD infrastructure has EKS Enabled.

• A Tenant named dev01 has been created.

• A Host named host01 has been created.

• A Service named demo-service has been created.

• An HTTPS Application Load Balancer has been created.

Testing the Application

Note that if you skipped Step 7 and/or Step 8, the configuration in the Other Settings and DNS cards appears slightly different from the configuration depicted in the screenshot below. These changes do not impact you in testing your application, as these steps are optional. You can proceed to test your app with no visible change in the output of the deployable application.

1. In the Tenant list box, select the dev01 Tenant.

2. In the DuploCloud Portal, navigate to Kubernetes -> Services. The Services page displays.

3. From the Name column, select demo-service.

4. Click the Load Balancers tab.

5. In the DNS status card, click the Copy Icon ( ) to copy the DNS address displayed to your clipboard.

   
6. Open a browser instance and Paste the DNS in the URL field of your browser.

7. Press ENTER. A web page with the text Hello World! is displayed, from the JavaScript program residing in your Docker Container running in demo-service, which is exposed to the web by your Load Balancer.

Web page with Hello World! displayed

It can take from five to fifteen (5-15) minutes for the DNS Name to become active once you launch your browser instance to test your application.

Congratulations! You have just launched your first web service on DuploCloud!

Reviewing What You Learned

In this tutorial, your objective was to create a cloud environment to deploy an application for testing purposes, and to understand how the various components of DuploCloud work together.

The application rendered a simple web page with text, coded in JavaScript, from software application code residing in a Docker container. You can use this same procedure to deploy much more complex cloud applications.

In the previous steps, you:

• Created a DuploCloud Infrastructure named NONPROD: a Virtual Private Cloud instance backed by an EKS-enabled Kubernetes cluster.
• Created a Tenant named dev01 in Infrastructure NONPROD. While generating the Infrastructure, DuploCloud created a set of templates (Plan) to configure multiple AWS and Kubernetes components needed for your environment.
• Created an EC2 host named host01, providing the application with storage resources.
• Created a Service named demo-service to connect the Docker containers and associated images housing your application code to the DuploCloud Tenant environment.
• Created an ALB Load Balancer Listener to expose your application via ports and backend network configurations.
• Verified that your web page rendered as expected by testing the DNS Name exposed by the Load Balancer Listener.

Cleaning Up Your Tutorial Environment

In this tutorial, you created many artifacts for testing purposes. Now that you are finished, clean them up so others can run this tutorial using the same names for Infrastructure and Tenant.

1. To delete the dev01 tenant follow these instructions, then return to this page. As you learned, the Tenant segregates all work in one isolated environment, so deleting the Tenant you created cleans up most of your artifacts.
2. Finish by deleting the NONPROD Infrastructure. In the DuploCloud Portal, navigate to Administrator -> Infrastructure. Click the Action menu icon () for the NONPROD row and select Delete.

The NONPROD Infrastructure is deleted and you have completed the clean-up of your test environment.

Thanks for completing this tutorial and proceed to the next section to learn more about using DuploCloud with AWS.