Try it free

Deploy EdgeConnect on Kubernetes without Dynatrace Operator

  • Latest Dynatrace
  • How-to guide
  • 8-min read
  • Published Nov 06, 2026

Run EdgeConnect inside a Kubernetes cluster using a Deployment manifest plus Kubernetes Secrets for OAuth credentials and configuration. Use this manual deployment when Dynatrace Operator isn't installed.

Prerequisites

Create the EdgeConnect configuration in Dynatrace.

Run EdgeConnect in Kubernetes without Dynatrace Operator

Complete the following steps to deploy EdgeConnect on Kubernetes without Dynatrace Operator.

Step 1 Ensure connectivity

Before you apply the manifest, open the outbound network paths that EdgeConnect needs, then verify from the cluster that each one is reachable.

Allow outbound connections from the cluster to the following endpoints:

  • https://sso.dynatrace.com/sso/oauth2/token
  • https://<your environment ID>.apps.dynatrace.com

EdgeConnect doesn't require any inbound connection from Dynatrace.

Also allow connectivity from the cluster to any application in your network that you want Dynatrace to reach from app functions, ad hoc functions, or workflow actions. If EdgeConnect communicates behind an HTTPS proxy, you also need to add the trusted certificates of the hosts EdgeConnect connects to. If the proxy performs TLS interception, also add the certificate of the proxy itself. For instructions, see Add custom TLS certificates.

Step 2 Configure EdgeConnect deployment

The edgeConnect.yaml file contains the configuration values required to deploy EdgeConnect. Use those values to customize the deployment manifest.

  1. Download the edgeConnect.yaml file.
  2. Save the following example as deployment.yaml.
  3. Replace the values surrounded by < > with the corresponding value from edgeConnect.yaml.
apiVersion: v1
kind: Secret
metadata:
name: edge-connect-oauth
namespace: dynatrace
stringData:
oauth-client-id: <oauth.client_id from edgeConnect.yaml>
oauth-client-secret: <oauth.client_secret from edgeConnect.yaml>
---
apiVersion: v1
kind: Secret
metadata:
name: edge-connect-config
namespace: dynatrace
stringData:
edge-connect-config-file: |
certificate_paths:
- "/etc/edge_connect_certs/some_certificate.cer"
- "/etc/edge_connect_certs/another_certificate.pem"
secrets:
- name: My secret
token: dt0e01.some-token-name.some-token-secret
from_env: MY_SECRET
restrict_hosts_to:
- dynatrace.com
- name: My other secret
token: dt0e01.another-token-name.another-token-secret
from_file: /path/to/my/other/secret
restrict_hosts_to:
- internal.example.com
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: example-edge-connect
namespace: dynatrace
spec:
replicas: 1
selector:
matchLabels:
app: edge-connect
template:
metadata:
labels:
app: edge-connect
spec:
containers:
- name: edge-connect
image: dynatrace/edgeconnect:latest
imagePullPolicy: IfNotPresent
env:
- name: EDGE_CONNECT_NAME
value: <name from edgeConnect.yaml>
- name: EDGE_CONNECT_API_ENDPOINT_HOST
value: <api_endpoint_host from edgeConnect.yaml>
- name: EDGE_CONNECT_OAUTH__ENDPOINT
value: <oauth.endpoint from edgeConnect.yaml>
- name: EDGE_CONNECT_OAUTH__RESOURCE
value: <oauth.resource from edgeConnect.yaml>
volumeMounts:
- name: secrets
mountPath: "/etc/edge_connect"
readOnly: true
- name: config
mountPath: "/edgeConnect.yaml"
subPath: "edgeConnect.yaml"
readOnly: true
volumes:
- name: secrets
secret:
secretName: edge-connect-oauth
items:
- key: oauth-client-id
path: oauth/client_id
- key: oauth-client-secret
path: oauth/client_secret
- name: config
secret:
secretName: edge-connect-config
items:
- key: edge-connect-config-file
path: edgeConnect.yaml

The example edge-connect-config Secret includes a certificate_paths and a secrets block. For what these entries do and the Kubernetes volumes they need, see Add custom TLS certificates and Inject secrets into requests.

You can configure EdgeConnect in Kubernetes in three ways. Choose the one that fits your setup, or combine them.

Environment variables

You can use environment variables to configure most EdgeConnect settings. For the full field descriptions, see edgeConnect.yaml field descriptions.

Mapped files

You can provide configuration values through files mounted under /etc/edge_connect. EdgeConnect maps each file path to the corresponding .yaml fields. Using a mapped file has the same effect as setting the equivalent environment variable.

For example:

  • /etc/edge_connect/name maps to the name field in edgeConnect.yaml, which is equivalent to setting the EDGE_CONNECT_NAME environment variable.
  • /etc/edge_connect/oauth/client_id maps to oauth.client_id in edgeConnect.yaml, which is equivalent to setting the EDGE_CONNECT_OAUTH__CLIENT_ID environment variable.

All configuration values that can be set with environment variables, as documented in edgeConnect.yaml field descriptions, can also be configured using mapped files.

Mount edgeConnect.yaml

You can mount edgeConnect.yaml directly in the EdgeConnect container. Note that some settings can only be configured this way, for example secrets (see the secrets field descriptions).

Step 3 Apply the deployment

  1. Go to the directory containing the deployment.yaml file you created.

  2. Apply the deployment.

    kubectl apply -f ./deployment.yaml

Step 4 Validate the connection

Confirm that EdgeConnect successfully connected to the platform.

  1. Go to Settings Settings > General > External Requests > EdgeConnect.

  2. Check the Availability column. The column should display online.

    • If it's still offline, check the container logs for error messages.
    • If the app shows online EdgeConnect instances, your environment is now safely connected to the Dynatrace platform.

Any HTTP request from an app function, ad hoc function, or workflow action whose target host matches a configured host pattern runs transparently through EdgeConnect instead of directly through the Dynatrace runtime.

Next steps

  • To add custom TLS certificates or inject secrets into outgoing requests, see Configure TLS certificates and secrets for EdgeConnect.
  • To deploy with Dynatrace Operator instead, see Set up EdgeConnect with Dynatrace Operator.
  • To let Dynatrace Operator create and manage the configuration as well, see Provision EdgeConnect for a Dynatrace environment.
  • To verify which configuration handles a URL and set up host mappings, see Test EdgeConnect routing and configure host mappings.
  • For multi-cluster scenarios where the same hostname appears in several environments, see Manage multiple EdgeConnect configurations.

Related topics

  • EdgeConnect concepts
  • EdgeConnect reference
  • Get started with EdgeConnect
Related tags
Infrastructure Observability