How dynatrace operator with OA pulled image will know about new routing AG?

[Yosi_Neuman]

Hi guys,

Will be happy to read your suggestions for the follow scenario:

1. K8S with no connection to the cluster nodes on port 443 nor to AG's on port 9999, from pods
2. Installing dynatrace operator with pulled OA image

How the OA pods will connect to the routing AG if the ip is not publish yet and not included in the pulled  image?

Do we need to install first StatefullSet AG and not to install the AG from the dynatrace operator?

Maybe just to pull new image from dynatrace after routing OA is up an running and push the new image to the OA pods?

Thanks in advance for your inputs here

All the best and stay safe

Yos 

[ChadTurner]

So we have it all defined in Helm, so deployment looks directly at a DNS Alias which holds a set of AGs for the Oneagent Version, then it gets installed to the nodes, and then they report back via Network Zones to specific AGs. 

[Yosi_Neuman]

Hi @ChadTurner ,

Thanks for your replay

My bad, forgot to mention that in this case customer uses PSP so we utilized dynatrace operator V0.2.1 which is the last version that support PSP, after no host was added to cluster we saw in OA pods os logs that it tries to reach the cluster and other AGs and not to the new born routing AG, hence we docker pulled newer OA version from cluster and pushed it to the local repository and after deleting the OA pods it took the new OA version and hosts appeared in the dynatrace UI in no time. so the question remains  what is the right why to do this ? is there some setting from cr.yaml that can do the trick?

Thanks in advance 

Yos 

[IzabelaRokita]

Hey @Yosi_Neuman, did you manage to find the solution to your problem? If so, it would be amazing if you've shared it with the rest of the Community! If not, let me know, and I'll look for some further assistance 😊

[Yosi_Neuman · Accepted solution]

Hi @IzabelaRokita 

We found out that we can set the server end point for AG and OA from entries within the dynakube.yaml 

For OA under args:

      # Optional: Adds custom arguments to the OneAgent installer
      # For a list of available options, see https://www.dynatrace.com/support/help/shortlink/linux-custom-installation
      # For a list of the limitations for OneAgents in Docker, see https://www.dynatrace.com/support/help/shortlink/oneagent-docker#limitations
      #
      # args: []

For AG under customProperties:

    # Optional: Defines a custom properties file, the file contents can be provided either as a value in this yaml or as a reference to a secret.
    # If a reference to a secret is used, then the file contents must be stored under the 'customProperties' key within the secret.
    #
    # customProperties:
    #   value: |
    #     [connectivity]
    #     networkZone=
    #   valueFrom: myCustomPropertiesSecret

HTH

Yos