App Delivery Network (ADN)

This example creates a sample namespace called tutorial-hipster namespace.

• Select the Administration service.
• Select Personal Management > My namespaces.

• Click Add namespace and enter a name for your namespace. Click Save changes to complete creating the namespace.

• Change to the Distributed Apps service.

• Click on the application namespace option on the namespace selector. Select the namespace created in previous step from the namespace dropdown list to change to that namespace.

• Select Applications in the configuration menu and Virtual K8s in the options pane.

  

• Click Add Virtual K8s and enter a name for your vK8s cluster.

• Click the Select vsite ref button and select ves-io-all-res. Click the Select Vsite Ref button at the bottom to apply the virtual site to the vK8s configuration.

• Click Save and Exit to start creating the vK8s clusters in all RE sites.

• Once the vK8s object is created, click ...> Kubeconfig for it and enter an expiration date to download its kubeconfig file.

To deploy the web application in a K8s cluster, the following are required:

• Kubeconfig of the K8s cluster. For this, use the vK8s kubeconfig downloaded in previous step.
• Manifest file of your web application. Download the sample this example uses and edit its fields as per your application.

Enter the following command to deploy the application:

          kubectl --kubeconfig ves_adn_adn.yaml --namespace adn apply -f kubernetes-manifests.yaml

        

Note: You can download the kubectl application here: kubeclt.

This completes deployment of application across all RE sites.

• Select the Multi-Cloud App Connect service.
• Select the namespace created in step 1.1 where we previously deployed our application onto our vk8.
• Navigate to Manage in the left menu. Select Load Balancers > HTTP Load Balancers from the options. Click Add HTTP Load Balancer to start load balancer creation.

• Enter a name for the load balancer.
• Under Domains and LB Type in the List of Domains field, enter the domain(s) that will be matched to this load balancer.
• Select the Load Balancer Type. For this quick start, we will select HTTPS with Automatic Certificate.

• Scroll down to the Origins section and click Add Item to set up an origin pool.

• Use the Origin Pool pull-down menu to find and click the Create new origin pool button.

• Enter a name for the new origin pool.

• In the Origin Servers section, click Add Item.

  • In the Select Type of Origin Server field, select K8s Service Name of Origin Server on given Sites.
  • Enter a name in the Service Name field in the form <unique-name>.<namespace>. For the quick start example, we'll enter frontend.adn.
  • Set this as a Virtual Site in the Site or Virtual Site field.
  • Set the virtual site to the same site used when you created your virtual kubernetes cluster. In this example, we used ves-io-all-res.
  • For the Select Network on the site field, select vK8s Networks on Site.
  • Click Add Item to save the origin server.

  

• Enter the port number that the origin server is using.

• Click Continue at the bottom of the page to create the origin pool.

• Click Add Item to add this pool to the HTTP load balancer.
• Click Save and Exit to complete the HTTP load balancer.
• Press the Refresh button to update the TLS info column in the load balancer table. After a few minutes, the TLS info will be certified, and we'll be able to access our application through the domain we specified.

• Select the Web App & API Protection service.

• Select the namespace used to create the http load balancer previously.

• Navigate to Manage > Load Balancers > HTTP Load Balancers.

• Click ...>Manage Configuration for your load balancer, and then click Edit Configuration in the top right to edit the load balancer's configuration.

• Scroll down or click on Security Configuration in the left menu to go to the security configuration section.

• Select Enable in the Web Application Firewall (WAF) field.

• In the Enable field, click the Create new App Firewall button (use the pull-down menu to see the button.

  

Perform the configuration using the following guidelines:

• Enter a name for the Distributed Cloud WAF in the Metadata section.
• Set the Enforcement Mode to Blocking to protect the website. The other default option is Monitoring, which will log malicious activity, but it will not block any traffic.
• Leave the Detection Settings at their defaults.
• Click Continue to complete creating the WAF.

• Click Save and Exit to add the WAF to the load balancer configuration.

• Log into the Console and select the Distributed Apps service.
• Change to your namespace.
• Click App Site Map in the Sites section to get a global view of all your apps.

• Click on a site in the map to get details for that site. You can see the application's health overview along with a summary of requests and errors.

• In the sidebar menu, select Load Balancers > HTTP Load Balancers to see a list of HTTP load balancers.
• Find your load balancer in the list and select Performance Monitoring. This shows the performance dashboard showing the overall status such as a health score, the number of origin servers, end-to-end latency, requests per second, and throughput information.

• Click Metrics tab check the metrics such as request rate, error rate, latency, and throughput.

• Click Traffic tab to see the request rate and overall throughput between source, load balancer, and origin server.

• Click Origin Servers tab check the origin servers and the associated details like requests, errors, latency, RTT, etc.

• In the sidebar menu, select Service Mesh to see a list of service meshes.
• Click on the More button associated with the service mesh object for your application to open its service graph. The service graph shows the service mesh graph for your application services.

• Click on an endpoint to see more details and health information.

• Click Explore Service to see more details

• Click the API Endpoints tab to display the distribution map of all requests hitting the app via local answer and shows the percentage split of each path per segment.

  

• Click the Dashboard tab to see latency distribution per service as well as request rate, latency, and throughput of services.