Skip to content

Getting Started

We have chosen to use an Agent Operator to manage our contrast deployments.

The agent operator manages 5 main Kubernetes Custom Resources, of which we only leverage 3:

  1. AgentConnection
  2. ClusterAgentConnection
  3. AgentConfiguration
  4. ClusterAgentConfiguation
  5. AgentInjector

The ClusterAgentConnection is be deployed to the Contrast agent operator namespace. (mlife-appsec)

The AgentConfiguration and AgentInjector are deployed into each application namespace.

The InfoSec team collaborates with Scalable Compute team to include deploy and manage these resources so app teams don't have to.

Any .NET application that desires to have Contrast Agent injected should include BOTH these labels on it's Kubernetes Deployment:

  • mlife.medtronic.com/inject-contrast: true
  • mlife.medtronic.com/contrast-agent: dotnet-core

Any Java application that desires to have Contrast Agent injected should include BOTH these labels on it's Kubernetes Deployment:

  • mlife.medtronic.com/inject-contrast: true
  • mlife.medtronic.com/contrast-agent: java

Environment Variables and Configurations:

The contrast agent operator will inject the AgentConfiguration, AgentConnection and AgentInjector which will configure all the environment variables. Therefore, no additional variables and configurations should be added to any of the deployment files.