enable automatic version updates for OneAgent/Activegate in a K8s

[Nakazato_IIM]

I don't know how to disable automatic version updates for OneAgent/Activegate in a Kubernetes environment.
I've read that I can disable this by specifying “autoUpdate: false” in 'dynakube.yaml' but I can't find that setting in the YAML file.
I also don't know how to set it to a specific version.

[Nakazato_IIM]

Correction

Disabling Automatic Updates

[DanielS · Accepted solution]

Hi @Nakazato_IIM I leave you the options you can use in the dynaKube YAML, by default autoupdate is enabled. But if you specify a particular version it will be tied to that version. I've never tried live that options.

apiVersion: dynatrace.com/v1beta6
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
spec:
  apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
  metadataEnrichment:
    enabled: true
  oneAgent:
    cloudNativeFullStack:
      tolerations:
        - effect: NoSchedule
          key: node-role.kubernetes.io/master
          operator: Exists
        - effect: NoSchedule
          key: node-role.kubernetes.io/control-plane
          operator: Exists

      # Optional: Disable automatic restarts of OneAgent pods in case a new version is available
      # autoUpdate: true

      # Optional: The OneAgent version to be used.
      # Example: <major>.<minor>.<release>.<timestamp>, e.g. 1.200.0.20240101-000000
      #
      # version: ""

  activeGate:
    capabilities:
      - routing
      - kubernetes-monitoring
      - dynatrace-api

    # Optional: Use a custom ActiveGate image
    # image: ""
    resources:
      requests:
        cpu: 200m
        memory: 6Gi
      limits:
        cpu: 1000m
        memory: 6Gi

[andre_vdveen]

Hi @Nakazato_IIM,

I assume this is what you're looking for: Configure auto-update for Dynatrace Operator managed components
Adding/omitting the image field controls whether it will update or not.

[sujit_k_singh · Accepted solution]

Hi @Nakazato_IIM 

The autoUpdate field existed in the older v1beta1 API version of the DynaKube custom resource. It has been deprecated and removed in the current v1beta6 or spec. If your dynakube.yaml uses v1beta6, that field simply doesn't exist anymore which is why you can't find it.

In the current v1beta6 API, there is no standalone autoUpdate: false flag. The only way to disable automatic updates is to pin a version using either the version field or the image field. Setting either one implicitly disables auto-update for that component.

My suggestion is use image when pulling from a private/mirrored registry. Use version when pulling from the default Dynatrace registry.

Thanks,

Sujit