Containers Orchestrator hands-on lab with Kubernetes

Enable OMS monitoring of containers

This expands on the steps described here by using a k8 secret to store the workspace id and key.

• Go to the OMS portal and get the workspace id and a key (see the page referenced in the prior link).
• Create a k8 secret to hold the workspace id and key. The following command creates a generic secret named oms-agent-secret that holds the properties WSID and KEY. Substitute your WorkspaceID and WorkspaceKey for the placholder values.

kubectl create secret generic oms-agent-secret --from-literal=WSID=<WorkspaceID> --from-literal=KEY=<WorkspaceKey>

Note two points in the file k8-demo-enable-oms.yml

• The deployment type is DaemonSet which means one instance will be deployed to each agent Node
• The reference to the secret created in the prior step to hold the OMS WorkspaceID and WorkspaceKey

Deploy the agent with the following command:

kubectl create -f k8-demo-enable-oms.yml

Within a few minutes you should see metrics and logs for containers deployed in the k8 cluster.

Lab Navigation

1. Lab Overview
2. Kubernetes Installation on Azure
3. Hello-world on Kubernetes
4. Experimenting with Kubernetes Features
   1. Placement
   2. Reconciliation
   3. Rolling Updates
5. Deploying a Pod and Service from a public repository
6. Create Azure Container Service Repository (ACR)
7. Enable OMS monitoring of containers <– You are here
8. Create and deploy into Kubernetes Namspaces

Back to Index