Cluster name not showing as expected .

[Vikas_g1997]

Hi Team,

We have onboarded the Kubernetes cluster, but the naming is not appearing as expected—it is only showing as dynakube. Could anyone please help identify the reason for this?

Please find below the snapshot of the current naming issue and the YAML file used for configuration for reference

 

[MostafaHussein]

interested

[rgarzon1]

Hi @Vikas_g1997 

the Yaml its ok, i cant find anything out of the line. the cluster must be name like the name in the metadata,

did you allready check 

maybe someone change the name manually and that its a priority

[Vikas_g1997]

Hi RGarzon1,

Thank you for your suggestion. If we use the default settings, it should revert to the detected name, correct?

[p_devulapalli]

@Vikas_g1997 , your yaml file already looks good, you don't need to change anything . You already seem to have defined the cluster name in dynakube.yaml

[Vikas_g1997]

Hi @p_devulapalli ,

Just a quick question do we require codemodules in dynakube.yaml?

apiVersion: dynatrace.com/v1beta1

kind: DynaKube

metadata:

  name: cnhb3prdomsaks01

  namespace: dynatrace

spec:

  apiUrl:

  dynatraceApiRequestThreshold: 15

  skipCertCheck: true

  tokens: cnhb3prdomsaks01

  activeGate:

    capabilities:

      - routing

      - kubernetes-monitoring

      - dynatrace-api

    image: public.ecr.aws/dynatrace/dynatrace-activegate:1.299.33.20240925-184604

    replicas: 1

    resources:

      limits:

        cpu: 1000m

        memory: 1.5Gi

      requests:

        cpu: 500m

        memory: 512Mi

  oneAgent:

    cloudNativeFullStack:

      autoUpdate: true

      image: public.ecr.aws/dynatrace/dynatrace-oneagent:1.297.63.20240905-133818

      codeModulesImage: public.ecr.aws/dynatrace/dynatrace-codemodules:1.297.63.20240905-133818

      tolerations:

      - effect: NoSchedule

        key: node-role.kubernetes.io/master

        operator: Exists

      - effect: NoSchedule

        key: node-role.kubernetes.io/control-plane

        operator: Exists

[rgarzon1]

Generally, I don’t use it (code modules), at least not when I'm using something distinct to application-only monitoring. Do you want to set it for a specific technology? If your goal is to make it all-purpose, then it's better not to set it

[p_devulapalli]

@Vikas_g1997 as @rgarzon1 mentioned codeModulesImage is not mandatory for Kubernetes monitoring, it is useful when you need to specify a custom OneAgent image to be injected into pods for monitoring in Kubernetes environment.

[gopher]

@Vikas_g1997   to override the detected cluster name: use the following feature annotation.
Enjoy

apiVersion: dynatrace.com/v1beta2

kind: DynaKube

metadata:

  name: dynakube

  namespace: dynatrace

  annotations:

    feature.dynatrace.com/automatic-kubernetes-api-monitoring-cluster-name: "${TF_VAR_cluster_name}"  

[Vikas_g1997]

HI @p_devulapalli and @gopher ,

Thank you for your guidance on this matter. Could you please provide suggestions on how we can manually update the OneAgent on an AKS cluster? Additionally, I would like to understand the recommended timeframe or interval at which the update process should be performed.