Exposes custom StatsD and EEC images in DynaKube ActiveGate spec

[toszr]

It is now possible to customize EEC & StatsD Docker images using feature flags feature-custom-eec-image & feature-custom-statsd-image. This is useful for customers who maintain private registries with Dynatrace images (and necessary for the time being until EEC & StatsD images are integrated with Dynatrace Docker registry).

CRD changes will follow once the DynaKube format is more stable.

# ...
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  annotations:
    "alpha.operator.dynatrace.com/feature-custom-eec-image": "registry.lab.dynatrace.org/eec/dynatrace-eec:latest"
    "alpha.operator.dynatrace.com/feature-custom-statsd-image": "registry.lab.dynatrace.org/datasource/dynatrace-datasource-statsd:latest"
# ...

[chrismuellner]

These images should be set by feature flag/annotation and not in the CR

[toszr]

These images should be set by feature flag/annotation and not in the CR

Why? They are customer-facing, same as the ActiveGate image property in the DynaKube CR. As I learned, some customers prefer to perform manual version upgrades and the same is true for image versions.

[chrismuellner]

These images are not yet available on the registry, so having the configurable allows us to test and use them without having to change the whole CR.
We can talk about adding them to the CR at a later stage, but for now configuring them via annotations is enough.

[toszr]

OK, it's a small change I can fit into the first release. Be it annotations then (custom-eec-image, custom-statsd-image)

Solved (switched from DynaKube properties to feature flags for EEC/StatsD images)

[chrismuellner]

PR Description should be updated to reflect move to annotations

[toszr]

PR Description should be updated to reflect move to annotations

Good catch, thanks, done.

Done