lookiinspire.blogg.se - Kubernetes annotations list

#Kubernetes annotations list update
#Kubernetes annotations list manual
#Kubernetes annotations list code
#Kubernetes annotations list download

Enrichment means the logs and data are related back to entities (pods, processes, hosts). Metadata metric enrichment leverages data from OneAgent and Dynatrace Operator by adding additional context or relevant data to the metrics sent.

#Kubernetes annotations list manual

When you're finished, you can return to the installation instructions for your manual (kubectl/oc) or helm deployment. Metadata metric enrichmentĪs part of getting started with Kubernetes monitoring, you may want to configure metadata metric enrichment. csiįor more configuration options, see Example security context constraints.

#Kubernetes annotations list download

Yaml copy download apiVersion: /v1 kind: Securit圜ontextConstraints metadata: name. Configure security context constraints (OpenShift)Īs part of getting started with Kubernetes monitoring, you may want configure security context constraints (SCC) for OpenShift.

#Kubernetes annotations list update

To get this feature, be sure to update Dynatrace Operator if you're using an earlier version. This certificate is automatically mounted into every container to /var/run/secrets/kubernetes.io/serviceaccount/ca.crt and merged into the ActiveGate truststore file using an initContainer. Kubernetes automatically creates a kube-root-ca.crt configmap in every namespace. Kubernetes API certificates are automatically imported for certification validation checks.

metadata: annotations: /technologies: "java,nginx" /flavor: "musl" /install-path: "/dynatrace" /installer-url: " Import Kubernetes API certificatesĪs part of getting started with Kubernetes monitoring, you may want to check how importing Kubernetes API certificates works. If set to false, the webhook will not modify the pod. If set to false, no metric enrichment file will be added to the pod. It defaults to the Dynatrace environment API configured on the API URL of DynaKube.Īll applicable pod annotations for applicationMonitoring with CSI driver: If set, it indicates the URL from where the OneAgent app-only package will be downloaded. It defaults to "/opt/dynatrace/oneagent-paas".

If set, it indicates the path where the unpacked OneAgent directory will be mounted.

#Kubernetes annotations list code

If set, it filters which code modules are to be downloaded. Note: If your container uses musl (for example, Alpine base image), you must add the flavor annotation in order to monitor it. If set, it indicates whether binaries for glibc or musl are to be downloaded. If set to false, no modifications regarding metric enrichment will be applied to the pod. If set to false, no modifications regarding OneAgent will be applied to the pod. If set to false, no modifications regarding OneAgent will be applied to the pod.ĭ/inject. inject: "true" Pod annotation listĪll applicable pod annotations for applicationMonitoring without CSI driver:ĭ/inject.

To add the custom properties file as a value, see the example below.

You can add a custom properties file by providing it as a value or by referencing it from a secret. Add a custom properties file optionalĪs part of getting started with Kubernetes monitoring, you may want to add a custom properties file. Note: The values aren't validated by Dynatrace Operator or the webhook, so make sure they are valid.

/build-version holds the fieldPath used for DT_RELEASE_BUILD_VERSION.

/stage holds the fieldPath used for DT_RELEASE_STAGE.

If this annotation is missing, mapping falls back to the default behavior.

/product holds the fieldPath used for DT_RELEASE_PRODUCT.

/version holds the fieldPath used for DT_RELEASE_VERSION.

Yaml copy download annotations: /version: "metadata.annotations" /product: "metadata.labels" /stage: "metadata.namespace" /build-version: "metadata.labels"Įach of these annotations configures a different environment variable: