topic Re: Change Environment to cluster Openshift in Automations

Change Environment to cluster Openshift

JAR — Thu, 09 Jun 2022 12:13:51 GMT

Hi all.
We have the integration with an Openshift cluster reporting in one environment (PRE), but we want to change it to another environment (DEV). Both environments are in the same Managed tenant.

What would be the best way to do it?
It is necessary to do a new installation?
Or is it enough to edit the dynakube.yaml file?

Environment URL
Dynatrace Operator token
ACtiveGate?
....Something else to keep in mind...

Thanks in advance

Jose A

Re: Change Environment to cluster Openshift

pahofmann — Thu, 09 Jun 2022 15:58:07 GMT

You mentioned the correct approach, you can just change the relevant entries in the dynakube yaml file.

Not 100% sure if it will redeploy the OneAgent pods automatically or if you have to cycle them once.

Re: Change Environment to cluster Openshift

JAR — Fri, 10 Jun 2022 07:19:32 GMT

Thank you very much for the reply pahofmann.

To confirm the steps:
1- edit yaml:

URL environment
DT operator TOKEn

2- redeploy one agent pod:
How is it done manually?

Thank you very much in advance

joseA

Re: Change Environment to cluster Openshift

pahofmann — Fri, 10 Jun 2022 07:36:43 GMT

As mentioned, not sure if the second is needed. You can just check after the update if it happens automatically and if not delete the OneAgent Pods yourself.

Now that I think about it, it will probably also require a restart of the deep monitored applications, so the code modules connect to the new environment.

Re: Change Environment to cluster Openshift

Sujit — Fri, 10 Jun 2022 07:46:11 GMT

@JAR Yes, you have to delete it as oneagent deployed as DeploymentSet so when you deleted it will create another OA automatically with updated new environment.

Re: Change Environment to cluster Openshift

pahofmann — Fri, 10 Jun 2022 14:06:27 GMT

Just realised there even is a documentation page for this: https://www.dynatrace.com/support/help/shortlink/migrate-operator-k8