The DETC POC project enables deploying a demo application into cloud accounts. Currently this project can provision a K8 cluster, deploy a small web app onto the cluster, install the Lacework monitoring pods onto the cluster and drive traffic over the web app. And of course all of the provisioned resources can be destroyed.

High level topics covered:

• Build DETC Docker image locally
• Provision a K8 Cluster
• Deploy the Vote app pods/services with Kubectl
• Deploy the Lacework pods with Kubectl
• Tearing it all down

Make sure to have all of these items ready before using this project:

• access to at least one cloud account with admin privileges
  • AWS
  • GCP
  • Azure
• access to a Lacework tenant with admin privileges
• Docker and docker-compose setup on a computer

terraform: 1.0.6 heroku cli: 7.59.0 kubectl: 1.22.1 helm: 3.0.2 aws cli: 1.20.48 azure cli: 2.0.81 gcp cli: 358.0.0

Each cloud account/cluster has a README file that covers how to get the cluster provisioned, because each cloud is special.

AWS EKS

Azure AKS

GCP GKE

note: below you will see some commands have '{{ K8-CLUSTER-ACRONYM }}', replace that with eks/aks/gke for the cluster type you have provisioned

Kubectl needs to be configured properly to communicate with the control plane for the cluster. Please refer to the README linked above to find out how to configure kubectl.

docker-compose run detc k8 {{ K8-CLUSTER-ACRONYM }} kubectl apply --deployment-path=/deploys/voteapp/vote.yml

To setup Lacework edit the '/docker-compose.yml' file set 'LACEWORK_ACCESS_TOKEN' to a valid a access token for the Lacework tenant being used. The access token can be found by opening the Lacework tenant in a browser and going to 'Setting' -> 'Agents'. There should be a clipboard icon that can be used to copy the access token.

docker-compose run detc lacework deploy-pods

Before deploying the load generation project use kubectl to get the URLs:

docker-compose run detc k8 {{ K8-CLUSTER-ACRONYM }} kubectl

Find the two externals URLs. The pod that is listening on port 5000 will go in the 'RESULT_URLS' field in the 'loadgen.js' file. The other URL will go in the 'VOTE_URLS' field in the 'loadgen.js' file.

Deploying the loadgen project

Outside the running apps and activity from load generation, the cloud enviornment may not have a ton of other activity depending on what it's used for. This deployment will create additonal activity in Azure/GCP using service accounts.

docker-compose run detc activity-generation [azure|gcp] init
docker-compose run detc activity-generation [azure|gcp] [plan|deploy|destroy]

All the provisioned assets can be destroyed.

First destroy any provisioned assets for the web app, mostly this is any external networking services.

docker-compose run detc k8 {{ K8-CLUSTER-ACRONYM }} kubectl destroy --deployment-path=/deploys/voteapp/vote.yml

Next destroy the provision cluster.

docker-compose run detc k8 {{ K8-CLUSTER-ACRONYM }} terraform destroy --skip-undeployment=true