This guide provides detailed steps for provisioning EdgeConnect for Kubernetes Connector using the Dynatrace Operator.
Create a new OAuth client the Dynatrace Operator uses
Create client
app-engine:edge-connects:connect
)app-engine:edge-connects:write
)app-engine:edge-connects:read
)app-engine:edge-connects:delete
)oauth2:clients:manage
)settings:objects:read
)settings:objects:write
)Create client
, the client is created and the following details visible on a subsequent page are generated by Dynatrace
urn:dtaccount:<your-account-uuid>
)Store the newly created OAuth client as a Kubernetes secret
Create a secret with the OAuth credentials.
apiVersion: v1kind: Secretmetadata:name: edgeconnect-oauthnamespace: dynatracestringData:oauth-client-id: <client id>oauth-client-secret: <client secret>
Apply the secret.
kubectl apply -f edgeconnect-oauth-secret.yaml
You need to configure and deploy EdgeConnect via the Dynatrace Operator. The Dynatrace Operator prepares EdgeConnect for Kubernetes Connector and configures the required connection in your Dynatrace tenant.
Configure the EdgeConnect custom resource file with serviceAccountName
(using the ServiceAccount deployed here), provisioner: true
, and kubernetesAutomation.enabled: true
properties.
apiVersion: dynatrace.com/v1alpha2kind: EdgeConnectmetadata:name: edgeconnect-deployment-rollout-restarternamespace: dynatracespec:apiServer: "<environment-id>.apps.dynatrace.com"serviceAccountName: edgeconnect-deployment-rollout-restarteroauth:provisioner: trueclientSecret: edgeconnect-oauthendpoint: https://sso.dynatrace.com/sso/oauth2/tokenresource: urn:dtaccount:<your-account-uuid>kubernetesAutomation:enabled: true
Apply the EdgeConnect custom resource.
kubectl apply -f edgeconnect.yaml
Rotating the OAuth credentials is not immediately reflected in the EdgeConnect deployment. This may lead to authentication issues until the Dynatrace Operator reconciles the EdgeConnect deployment.