Skip to main content

.NET Core installation and configuration in a container

Use this workflow with the Add New .NET Core agent wizard to ensure you have all the steps covered for installing and configuring the .NET Core agent with a container. Using the wizard is the simplest way to deploy a new agent.

Before you begin

Make sure you have everything you need before you start.

  • The agent will need to be able to reach your Contrast instance. It can be a local/on-premise instance or a hosted instance. A proxy can be configured if the environment has limited network access.

  • It must use supported technologies and system requirements.

  • Understand the order of precedence.

  • You will also need access to a command line interface (with a chosen directory for downloading the agent) and your organization's instance of Contrast.

Start the .NET Core agent wizard

  1. Open the agent wizard:

    • Northstar: From the left navigation, select Administration > Agent management. Then, select Add agent at the top of the view.

    • Contrast: Use either of these options:

      • From the header, select Add New and then, select the Application card.

      • Select Administration > Agent management. Then, select Add agent at the top of the view.

  2. Under Select a language, select .NET Core.

  3. Select the operating system you are using.

Select method to deploy with containers

  1. Under Select application deployment method, select Install in a container.

  2. Under Select method, to deploy containers, select Dockerfile or Kubernetes (Linux only).

Dockerfile: Build image with agent

  1. Under Build image with agent, copy the displayed commands and add them to your Dockerfile.

  2. Use the displayed command to build the image.

Dockerfile: Configure the agent

Under Configure the agent, select the best options to get the configuration details that the agent needs to communicate with Contrast. The following steps may or may not apply to your configuration steps.

  2. Optionally, select Register the application.

    When you register an application, you can assign it to groups for access control. You can also assign tags and metadata to the application.

  3. Select Use Connection Token.

    This configuration method uses a single variable to specify authentication values. The Connection Token is the recommended configuration option.

    Copy the displayed code and run the commands to pass the connection token to the container as an environment variable at startup.

Kubernetes: (Linux and OS X only)

  1. Under Select method to configure agent operator, select Helm (recommended) or Manifest.

  2. For Helm:

    1. Under Download and set up files, copy the displayed commands to create a values file. Skip this step if the operator is already installed.

    2. Under Install and deploy Helm chart, copy the displayed commands to complete the configuration. Skip this step if the operator is already installed.

    3. Label your namespaces to add AgentInjectors.

      kubectl label namespace/<YourNamespaceName> agents.contrastsecurity.com/agent-injectors=true

    4. Under Label the deployments, use the displayed commands to label your deployments.

  3. For Manifest:

    1. Under Install operator, copy the displayed commands to install the Contrast agent operator.

    2. Under Configure operator, copy the displayed commands to configure the Contrast agent operator.

    3. Under Configure injector, copy or download the clusterAgentInjector.yaml

    4. Label your namespaces to add AgentInjectors.

      kubectl label namespace/<YourNamespaceName> agents.contrastsecurity.com/agent-injectors=true

    5. Under Label the deployments, use the displayed commands to label your deployments.

    6. Optionally, under Configure cluster agent and cluster, copy the displayed commands to configure these entities.

Verify the agent deployment

  1. Interact with your application as you normally would. For example, interact with your application's web interface or send API commands.

  2. Select Administration, then Agent management to verify that your agent appears in the list.

  3. Verify that you see the name of your application in the list.

  4. Select Servers in the header.

  5. Verify that you see the name of your local server in the list.

In this section: