- we have deployed Dynatrace in Kubernetes (with Istio) using the dynatrace-operator (after removing oneagent-operator like recommended by Dynatrace)
- in the following documentation https://www.dynatrace.com/support/help/setup-and-configuration/setup-on-container-platforms/kubernet... is described that the oneagent-operator creates automatically the istio service entries
Is this done also automatically with the dynatrace-operator? If so, will the proxy parameter also be passed into the Istio service entry?
Solved! Go to Solution.
I'll Save you time,
It will create the Istio service entries for Dynatrace K8S Pods to communicate to the Active Gate, however it will not create the Namespace / Application Pods Istio Service entries.
You will be required to create Namespace / Application Pods Istio Service entries that allow communication from the Agents to Active Gate.
Suggest that you look at something like Terraform to manage that side of it, if your not already doing Infra as code.
I would recommend using something like Terraform (or equivalent managed infra code), where you can easily do this along side your namespace / pod deployment, it's pretty much a default to drop in where you want monitoring.
In Terraform, this can be handled like so, you just need to set the Active Gate CIDR variable as the Ingress address to where your Active Gate is deployed & has an Ingress / Egress flow (even if on the same cluster).
The above is a NetworkPolicy. It is not specific to Istio. And usually, most clusters by default will have NetworkPolicy disabled at creation. So this is specific to customer setup.
For Istio, the OneAgent/Dynatrace Operator can do this automatically with enableIstio: true
OneAgent Operator version 0.4+ automatically manages Istio service entries and virtual services for your Dynatrace environment when
enableIstiois set to
truein the custom resource. The Dynatrace OneAgent code modules can then send monitoring information to your Dynatrace environment.