Re: [I] Mapping key "cluster-autoscaler.kubernetes.io/safe-to-evict" already defined [airflow]

["elehcim (via GitHub)" <gi...@apache.org>]

elehcim commented on issue #38183:
URL: https://github.com/apache/airflow/issues/38183#issuecomment-2209071400

   > This also happens in a vanilla build of the helm chart using kustomize, so I don't think it's related to @nuvme-devops setup.
   > 
   > You can reproduce this by creating the following `kustomization.yml`:
   > 
   > ```yaml
   > # kustomization.yml
   > 
   > apiVersion: kustomize.config.k8s.io/v1beta1
   > kind: Kustomization
   > 
   > namespace: airflow
   > 
   > helmCharts:
   > - name: airflow
   >   releaseName: airflow
   >   version: "1.13.0"
   >   repo: https://airflow.apache.org
   > ```
   > 
   > And trying to build the template using `kustomize` with `--enable-helm`:
   > 
   > ```shell
   > kustomize build --enable-helm .
   > ```
   > 
   > Which gives the following error:
   > 
   > ```
   > Error: map[string]interface {}(nil): yaml: unmarshal errors:
   >   line 44: mapping key "cluster-autoscaler.kubernetes.io/safe-to-evict" already defined at line 43
   > ```
   > 
   > This indicates that the generated templates are invalid due to this duplicate key (which is maybe not checked in other contexts). The workaround @nuvme-devops works here as well, probably by avoiding those labels entirely.
   
   I can reproduce this with chart 1.14.0


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org