![]() Service Mesh Manager supports multiple mesh topologies, so you can use the one that best fits your use cases. Argo CD provides solutions to keep secrets safe. How to run SDM with upstream Istio in the same Kubernetes clusterĬAUTION: Do not push the secrets directly into the git repository, especially when it is a public repository.How to manage multiple Apache Kafka clusters using the dashboard.How to synchronize SDM resources between Kubernetes clusters.Synchronizing SDM resources across multiple Kubernetes Clusters.Using Kafka Connect with Streaming Data Manager.CruiseControlOperation to manage Cruise Control.OAuth Bearer Token Authentication for listeners (Apache Kafka pre 3.1.0).OAuth Bearer Token Authentication for listeners (Apache Kafka 3.1.0 and above).Enable OAuth Bearer Token Authentication for listeners.Client applications outside the Kubernetes cluster.Client applications outside the Istio mesh.Setup Istio to use CSR operator as external CA.Use a custom Certificate Authority with Istio.Updating the Kafka distribution with Streaming Data Manager.Managing custom Kafka distribution with Streaming Data Manager.Disaster recovery on Kubernetes using MirrorMaker2.Accessing the Streaming Data Manager binaries.The ApplicationManifest Custom Resource.Multi-cluster upgrade from 1.10.0 to 1.11.0.Please adapt the deployment manifest (i.e., Helm Chart) of the distributor component to leverage OAuth 2.0-based authentication. If you are integrating an external tool using the distributor component, you potentially use token-based authentication. Integration with open-source connector (distributor) Please adapt your HTTP requests to leverage OAuth 2.0-based authentication.īash copy download API-RESULT=$(curl -location -request POST ' cloudautomation:events:write' \ If you are sending HTTP requests to communicate with the API, you potentially add the x-token header to authenticate the request with the provided token. You can use your preferred JSON parser instead. Note: These instructions make use of jq, which is a tool to parse a JSON object for deriving the access token. header 'Content-Type: application/x-www-form-urlencoded') Plaintext copy download API-RESULT=$(curl -location -request POST ' cloudautomation:events:write' \ Test the OAuth 2.0 client for retrieving an access tokenĪuthenticate with your client ID and client secret obtained above to retrieve the access token: Note: The OAuth 2.0 client cannot have wider permissions than the user who requested the client. These settings are required for the Client credentials flow. Copy your client ID, client secret, and Dynatrace account URN.Read secrets - cloudautomation:secrets:read.Delete integrations - cloudautomation:integrations:delete.Write/Edit integrations - cloudautomation:integrations:write.Read integrations - cloudautomation:integrations:read.Write/Edit logs - cloudautomation:logs:write.Send events - cloudautomation:events:write.Read events - cloudautomation:events:read.Read resources - cloudautomation:resources:read.Select at least the following scopes for a typical third-party integration:.Under OAuth scopes, select Cloud Automation.Enter a client description and the user email.Select Accounts, and then select your account tile.In Dynatrace, go to the user menu and select Account settings.Please make sure that you trust the integration, verify its developers, and check what kind of information the integration is going to access. To authenticate the integration, the OAuth 2.0 client credentials flow is used. You can connect third-party integrations to your Cloud Automation instance. To interact with the Dynatrace Cloud Automation API, you can generate an OAuth 2.0 client (recommended), or use the Cloud Automation API token.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |