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.
Feature Request: Switch to disable all annotations / labeling
See original GitHub issueFeature request
As a DevOps engineer working on the CI/CD GH workflow, I want to disable all annotations and labeling that
K8s-Deploy GH action does, so they will not pollute K8s namespaces, deployments, pods, etc.
Now K8s-Deploy allows only disabling the namespace annotation but there is no way to disable pod labeling that does not work correctly.
Reason for turning off auto-annotations - I have a team-wide strategy for them so the GH action just pollutes K9s resources with labels and annotations that are not useful for my K8s resources.
NOTE:
There is a bug in K8s-Deploy GH action that does not properly sanitize the workflow name before using it as in the POD/Service/Deployment label.
E.g. my GitHub workflow name is “Build & Deploy Web Api” when K8s-Deploy calls kubectl to label all resources listed in the file it uses the following command
kubectl label -f /tmp/baked-template-12345.yaml workflowFriendlyName=Build_&_Deploy_Web_Api
so the label Build_&_Deploy_Web_Api contains invalid symbol & that is not allowed by K8s
Kubenetes - Label Syntax and character set
Issue Analytics
- State:
- Created a year ago
- Comments:9
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have fixed the docs 😃.
Will look into it. Thanks!