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.
Create the EdgeConnect configuration in Dynatrace.
Complete the following steps to deploy EdgeConnect on Kubernetes without Dynatrace Operator.
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/tokenhttps://<your environment ID>.apps.dynatrace.comEdgeConnect 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.
The edgeConnect.yaml file contains the configuration values required to deploy EdgeConnect. Use those values to customize the deployment manifest.
edgeConnect.yaml file.deployment.yaml.< > with the corresponding value from edgeConnect.yaml.apiVersion: v1kind: Secretmetadata:name: edge-connect-oauthnamespace: dynatracestringData:oauth-client-id: <oauth.client_id from edgeConnect.yaml>oauth-client-secret: <oauth.client_secret from edgeConnect.yaml>---apiVersion: v1kind: Secretmetadata:name: edge-connect-confignamespace: dynatracestringData:edge-connect-config-file: |certificate_paths:- "/etc/edge_connect_certs/some_certificate.cer"- "/etc/edge_connect_certs/another_certificate.pem"secrets:- name: My secrettoken: dt0e01.some-token-name.some-token-secretfrom_env: MY_SECRETrestrict_hosts_to:- dynatrace.com- name: My other secrettoken: dt0e01.another-token-name.another-token-secretfrom_file: /path/to/my/other/secretrestrict_hosts_to:- internal.example.com---apiVersion: apps/v1kind: Deploymentmetadata:name: example-edge-connectnamespace: dynatracespec:replicas: 1selector:matchLabels:app: edge-connecttemplate:metadata:labels:app: edge-connectspec:containers:- name: edge-connectimage: dynatrace/edgeconnect:latestimagePullPolicy: IfNotPresentenv:- name: EDGE_CONNECT_NAMEvalue: <name from edgeConnect.yaml>- name: EDGE_CONNECT_API_ENDPOINT_HOSTvalue: <api_endpoint_host from edgeConnect.yaml>- name: EDGE_CONNECT_OAUTH__ENDPOINTvalue: <oauth.endpoint from edgeConnect.yaml>- name: EDGE_CONNECT_OAUTH__RESOURCEvalue: <oauth.resource from edgeConnect.yaml>volumeMounts:- name: secretsmountPath: "/etc/edge_connect"readOnly: true- name: configmountPath: "/edgeConnect.yaml"subPath: "edgeConnect.yaml"readOnly: truevolumes:- name: secretssecret:secretName: edge-connect-oauthitems:- key: oauth-client-idpath: oauth/client_id- key: oauth-client-secretpath: oauth/client_secret- name: configsecret:secretName: edge-connect-configitems:- key: edge-connect-config-filepath: 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.
You can use environment variables to configure most EdgeConnect settings. For the full field descriptions, see edgeConnect.yaml field descriptions.
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.
edgeConnect.yamlYou 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).
Go to the directory containing the deployment.yaml file you created.
Apply the deployment.
kubectl apply -f ./deployment.yaml
Confirm that EdgeConnect successfully connected to the platform.
Go to
Settings > General > External Requests > EdgeConnect.
Check the Availability column. The column should display online.
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.