https://community.dynatrace.com/t5/Troubleshooting/AKS-WASM-node-pools-troubleshooting/ta-p/251156 <DIV class="lia-message-template-content-zone"> <P>On AKS, you can create node-pools specifically for running WASM workloads. However, these workloads cannot be injected.</P> <H2>What is a “WASM node-pool”?</H2> <P>According to the <A href="https://learn.microsoft.com/en-us/azure/aks/use-wasi-node-pools" target="_self">AKS documentation</A>:</P> <P>To determine if a node-pool is a “WASM node-pool,” check the <CODE>workload-runtime</CODE> of the node-pool. If its value is <CODE>WasmWasi</CODE>, then it is classified as a WASM node-pool. Example command:</P> <PRE><CODE>az aks nodepool show -g myResourceGroup --cluster-name myAKSCluster -n mywasipool --query workloadRuntime</CODE></PRE> <H2>What to do when using Dynatrace Operator in a cluster with a “WASM node-pool”</H2> <P>Dynatrace Operator cannot inject into pods running on nodes in a WASM node-pool. Therefore, you need to exclude these workloads from injection. There are a few ways to achieve this:</P> <UL> <LI>Use the <CODE>namespaceSelector</CODE> fields in the DynaKube configuration, assuming the setup ensures that only specific namespaces' pods run on WASM nodes.</LI> <LI>Apply pod-level annotations to enable or disable injection: <UL> <LI><CODE>oneagent.dynatrace.com/inject: "false"</CODE></LI> <LI><CODE>metadata-enrichment.dynatrace.com/inject: "false"</CODE></LI> </UL> </LI> </UL> <P><STRONG>Note:</STRONG> Since you have to explicitly create workloads that run on WASM nodes, annotating these workloads should not be much of a hassle.</P> </DIV> Mon, 22 Jul 2024 14:14:17 GMT darynakovyrina 2024-07-22T14:14:17Z https://community.dynatrace.com/t5/Troubleshooting/AKS-WASM-node-pools-troubleshooting/ta-p/251156 <DIV class="lia-message-template-content-zone"> <P>On AKS, you can create node-pools specifically for running WASM workloads. However, these workloads cannot be injected.</P> <H2>What is a “WASM node-pool”?</H2> <P>According to the <A href="https://learn.microsoft.com/en-us/azure/aks/use-wasi-node-pools" target="_self">AKS documentation</A>:</P> <P>To determine if a node-pool is a “WASM node-pool,” check the <CODE>workload-runtime</CODE> of the node-pool. If its value is <CODE>WasmWasi</CODE>, then it is classified as a WASM node-pool. Example command:</P> <PRE><CODE>az aks nodepool show -g myResourceGroup --cluster-name myAKSCluster -n mywasipool --query workloadRuntime</CODE></PRE> <H2>What to do when using Dynatrace Operator in a cluster with a “WASM node-pool”</H2> <P>Dynatrace Operator cannot inject into pods running on nodes in a WASM node-pool. Therefore, you need to exclude these workloads from injection. There are a few ways to achieve this:</P> <UL> <LI>Use the <CODE>namespaceSelector</CODE> fields in the DynaKube configuration, assuming the setup ensures that only specific namespaces' pods run on WASM nodes.</LI> <LI>Apply pod-level annotations to enable or disable injection: <UL> <LI><CODE>oneagent.dynatrace.com/inject: "false"</CODE></LI> <LI><CODE>metadata-enrichment.dynatrace.com/inject: "false"</CODE></LI> </UL> </LI> </UL> <P><STRONG>Note:</STRONG> Since you have to explicitly create workloads that run on WASM nodes, annotating these workloads should not be much of a hassle.</P> </DIV> Mon, 22 Jul 2024 14:14:17 GMT https://community.dynatrace.com/t5/Troubleshooting/AKS-WASM-node-pools-troubleshooting/ta-p/251156 darynakovyrina 2024-07-22T14:14:17Z