I think this is needed to fix a gofmt error:

diff --git a/src/kubeobjects/affinity.go b/src/kubeobjects/affinity.go
index dd00c1c7..ccf0f184 100644
--- a/src/kubeobjects/affinity.go
+++ b/src/kubeobjects/affinity.go
@@ -8,10 +8,10 @@ const (
        kubernetesArch = "kubernetes.io/arch"
        kubernetesOS   = "kubernetes.io/os"

-       amd64 = "amd64"
-       arm64 = "arm64"
+       amd64   = "amd64"
+       arm64   = "arm64"
        ppc64le = "ppc64le"
-       linux = "linux"
+       linux   = "linux"
 )

Good news!

We are excited to merge this pull request based on an agreement between Dynatrace and IBM as follows:

• Dynatrace will publish Dynatrace Operator container images for ppc64le as part of our Github Actions release pipeline
• IBM will recommend a standard configuration to our joint customers as observed in ppc64le lab environments.
  • Dynatrace Classic Full-Stack
  • NodeJS, nginx, and Java applications running in glibc containers
  • Kubernetes API monitoring via Dynatrace ActiveGate on an x86 architecture
• Known issues with unique kubernetes node identification such that multiple nodes may appear as one.
• IBM will recommend specific versions of the Dynatrace Operator to joint customers after ppc64le images are made available in a public registry.
• The Dynatrace Operator team will collaborate with IBM, and joint customers, to bring OpenShift observability to ppc64le in the spirit of this partnership.

Customer support issues, involving the Dyantrace Operator, which cannot be reproduced by Dynatrace on x86 or ARM and are determined to be ppc64le should be directed to IBM at dt-operator@ibm.com

Good news!

We are excited to merge this pull request based on an agreement between Dynatrace and IBM as follows:

• Dynatrace will publish Dynatrace Operator container images for ppc64le as part of our Github Actions release pipeline

• IBM will recommend a standard configuration to our joint customers as observed in ppc64le lab environments.

  • Dynatrace Classic Full-Stack
  • NodeJS, nginx, and Java applications running in glibc containers
  • Kubernetes API monitoring via Dynatrace ActiveGate on an x86 architecture

• Known issues with unique kubernetes node identification such that multiple nodes may appear as one.

• IBM will recommend specific versions of the Dynatrace Operator to joint customers after ppc64le images are made available in a public registry.

• The Dynatrace Operator team will collaborate with IBM, and joint customers, to bring OpenShift observability to ppc64le in the spirit of this partnership.

Customer support issues, involving the Dyantrace Operator, which cannot be reproduced by Dynatrace on x86 or ARM and are determined to be ppc64le should be directed to IBM at dt-operator@ibm.com

Helllo @chrismuellner

When will this be available?

Regards,

Babar

@bqayyum these changes are available since v0.12.0 (release notes in official documentation) released in june.