ActiveGate crashes on IPv6 only mode about dynatrace-operator HOT 2 CLOSED

Thanks for reporting this issue.
I'll close this here as it's not connected to the dynatrace-operator and have forwarded it to the ActiveGate team internally.

from dynatrace-operator.

@chrismuellner could you please follow this up internally? This issue is still not fixed.

I am not entirely sure if it is only connected to the ActiveGate since the format for the IPv6-address is provided in the StatefulSet of the ActiveGate as it is defined by the operator? Or did you mean that the env var should already include the square brackets?

        containers:
        - env:
          - name: DT_DNS_ENTRY_POINT
            value: https://$(DYNAKUBE_ACTIVEGATE_SERVICE_HOST):$(DYNAKUBE_ACTIVEGATE_SERVICE_PORT)/communication,https://dynakube-activegate.dynatrace:$(DYNAKUBE_ACTIVEGATE_SERVICE_PORT)/communication

Regardless of which team is responsible, this issue is still not fixed and prevents Dynatrace to be used in an IPv6 only Kubernetes-Environment.

from dynatrace-operator.