vlaborie opened a new issue, #18340:
URL: https://github.com/apache/dolphinscheduler/issues/18340

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   I tried to install DolphinScheduler Helm chart with FluxCD but i have the 
following error:       
   
   ```
    Helm install failed for release dolphinscheduler-staging/dolphinscheduler 
with chart [email protected]+5d9b388dad62: error while running post 
render on manifests: yaml: unmarshal errors:
             line 23: mapping key "app.kubernetes.io/name" already defined at 
line 22
   ```
   
   ### What you expected to happen
   
   Helm install function properly with FluxCD, no duplicated label.
   
   ### How to reproduce
   
   Use `helm template dolphinscheduler . -f custom-values.yaml` with configured 
`api.customizedConfig`, ex:
   
   ```
       api:
         enableCustomizedConfig: true
         customizedConfig:
           application.yaml: |
             YOUR_CONFIG
   ```
   
   The returning ConfigMap have duplicate `app.kubernetes.io/name` label:
   
   ```
   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: dolphinscheduler-api
     labels:
       app.kubernetes.io/name: dolphinscheduler-api
       app.kubernetes.io/name: dolphinscheduler-api
       app.kubernetes.io/component: api
       app.kubernetes.io/instance: dolphinscheduler
       app.kubernetes.io/managed-by: Helm
   data:
     application.yaml: |
   ```
   
   Tools like FluxCD exit with YAML error on this.
   
   ### Anything else
   
   I have an incoming PR for this.
   
   ### Version
   
   dev
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to