Step 6: Test your application
Test the application to ensure you get the results you expect
Last updated
Was this helpful?
Test the application to ensure you get the results you expect
Last updated
Was this helpful?
You can test the sample web page application directly from the VIEWWEBSITE Ingress that you created in the previous step.
Estimated time to complete Step 6 and finish tutorial: 10 minutes.
Before testing your application, ensure that:
Previous steps in this tutorial to create an Infrastructure and Plan, Tenant, Azure Agent Pool, Service, and Load Balancer Listener are complete.
AKS Kubernetes cluster is enabled.
Tenant dev01 is selected in the Tenant list box, at the top of the DuploCloud Portal.
You defined an Ingress and a rule for your DuploCloud Service to listen on port 80, enabled the App Gateway Ingress Controller, and configured a Load Balancer Listener that uses K8S Node Port.
Display the web page that the application creates:
In the DuploCloud Portal, navigate to Kubernetes -> Ingress.
Select the VIEWWEBSITE Ingress from the Name column.
Click the Configuration tab.
In the Application Gateway IP card, copy the displayed IP address to your clipboard. In this example, the IP address is 20.84.11.154.
Open a web browser and paste the copied IP address in your browser's URL field.
Press Enter. Your application runs and your web page renders as shown below. Congratulations! You just launched your first web service with Azure on DuploCloud!
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 AKS-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 Azure and Kubernetes components needed for your environment.
Created an Azure Agent Pool backed by pre-existing hosts (VMs), so that your application has storage resources with which to run.
Created a Service to connect the Docker containers and associated images, in which your application code resides, to the DuploCloud Tenant environment.
Created a Load Balancer Listener and a Kubernetes Node Port to expose your application via ports and backend network configurations. You enabled an Azure application gateway and created a Kubernetes Ingress to communicate with the node port and the AKS-enabled Kubernetes cluster in the Infrastructure.
Verified that your web page rendered as expected by testing the IP address exposed by the Kubernetes Ingress.
In this tutorial, you created many artifacts for testing purposes. When you are ready, clean them up so that another person can run this tutorial from the start, using the same names for Infrastructure and Tenant.
To delete the dev01 tenant follow these instructions and then return to this page. As you learned, the Tenant segregates all work in one isolated environment, so deleting the Tenant that you created cleans up most of your artifacts.
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 Microsoft Azure.
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.
