Deploying a multi-service, cloud-native application on IKS leveraging IST


By 2025, Gartner estimates that over 95% of new digital workloads will be deployed on cloud-native platforms, up from 30% in 2021. As enterprises embrace cloud platforms, legacy Tomcat applications (for example), will also be rearchitected. The use case for the deployment of cloud native applications on the new breed of cloud platforms is what we will address in this blog.

In the first blog of this series, we looked at building workflows around IST (Intersight Services for Terraform) automations to provision IKS (Intersight Kubernetes Service) infrastructure and deploy a sample cloud native application with ICO (Intersight Cloud Orchestrator).

In part 2 and part 3, we leveraged IST and ICO to do a complete deployment of a multi service Tomcat application and instrumentation for AppDynamics insights. In this and the next blog, we will address the deployments of the cloud-native version of the same Tomcat application.

Use Case

Let’s take a look at a use case of deploying a multi-service, cloud-native application on IKS leveraging IST. As a value add, the TFCB (Terraform for Cloud Business) workspaces will include AppDynamics Cluster Agent for Application insights.

In the above diagram, each of the blocks refer to a TFCB workspace involving all the relevant resource provisioning. As you can see, there is a dependency in the execution of the various workspaces:

  • Set up the global variables
  • Set up the infrastructure including the IKS k8s cluster
  • Setup the AppDynamics Controller RBAC entities
  • Setup the k8s metrics server
  • Setup the AppDynamics Cluster Agent
  • Deploy App servicesGenerate Application load

Please check out this entry in DevNet Code Exchange for detail on this use case

Up next

In the next blog, we’ll explore ICO (Intersight Cloud Orchestrator) workflows to capture the above dependency of the TFCB workspaces.

Additional Resources

 


We’d love to hear what you think. Ask a question or leave a comment below.
And stay connected with Cisco DevNet on social!

LinkedIn | Twitter @CiscoDevNet | Facebook Developer Video Channel

 

Share:





Source link