Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Duplicate app.kubernetes.io/instance labels keys breaks kustomize
See original GitHub issueDescribe the bug
There is a duplicate label key app.kubernetes.io/instance: ambassador in the ambassador-agent deployment which breaks kustomize.
Remove the duplicate keys
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Issues - GitHub
There is a duplicate label key app.kubernetes.io/instance: ambassador in the ambassador-agent deployment which breaks kustomize. Remove the ...
Read more >Helm chart generated yaml is invalid - (Kustomize parse errors)
I'm looking at a generated output from helm template TEST gitlab/gitlab -f config.yaml , and I do see duplicate app: labels .. #...
Read more >Declarative Management of Kubernetes Objects Using ...
Kustomize will automatically replace this name with the generated name. This is an example deployment that uses a generated ConfigMap: # Create ...
Read more >CI/CD OpenShift Container Platform 4.11
Creating CI/CD solutions for applications using OpenShift Pipelines ... labels: app.kubernetes.io/instance: default app.kubernetes.io/part-of: ...
Read more >Kubernetes at Home With K3s - Bruno Antunes
But why I know what you're thinking - Kubernetes? ... portainer app.kubernetes.io/instance: portainer template: metadata: labels: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Whoops sorry about that, thanks for pointing that out. I’ll make sure that gets in the next release
The fix for this went out in chart 6.7.11