Kubernetes monitoring activegate configuration

[thitiphans]

Hi right now when deploy agent using operator. document here 

this will create new activegate for k8s and use it.

but I want to use existing active gate where and how I should config.

currently I try change custom resource on apiurl but it didn't work

[Mizső]

Hi @thitiphans,

As far as I know you have two options.

1. Use the containerized active gate (one or more - scale up in the dynakube resouce yaml)

2. Use the existing active gates by comment out the active gate in the  dynakube resource yaml

I guess you can't use together. ☹️

Br, Mizső

[thitiphans]

Thank you for your reply. 

What I planned to do is use only existing activegate.

You mention that need to comment out dynakube yml file is it "routing" line?

Currently there is active gate which on public subnet but I want to monitor k8s which in private subnet can't connect to public internet. 

[pahofmann · Accepted solution]

If you have the activegate section in the cr.yaml but don't wan't an AG deployed just delete or comment out the entire section.  

If you have an external AG that the agents can reach they will use it for routing automatically.

For the k8s API integration with an non operator AG follow this:

https://www.dynatrace.com/support/help/shortlink/ag-k8s-vm#connect-clusters-to-dynatrace

You can also use the operator AG just for traffic routing and not the API integration. In that case leave the activegate section in the CR but make sure the annotation mentioned here is not set:

https://www.dynatrace.com/support/help/shortlink/deploy-ag-dynatrace-op#local 

You can also remove the  - kubernetes-monitoring capability.