-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm custom labels (#369) #370
Conversation
Provide the support for global custom labels.
fix typo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few small fixes.
Co-authored-by: Michał Flendrich <m.flendrich@gmail.com>
Update according feedback.
Fix typo.
@mflendrich I got one another issue to fix, so what is the process for merging this PR ? Thanks ! |
@ludovic-pourrat there's currently some conflict between it and current next that blocks the merge. You'll want to update your copy of next with upstream changes, merge next into your branch, fix conflicts that occur during the merge, and then push the result. |
@rainest fork up-to-date mow. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
post one comment
|
||
```yaml | ||
extraLabels: | ||
acme.com/some-key: some-value |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would suggest using format
acme.com/some-key: "{{.value}}"
Ah the damn Github UI was complaining about rebase merge mode only. That should probably have some UI indicator that a squash merge won't cause conflicts :| no matter. Thank you for your contribution. Please fill out the following form to claim your contributor swag: |
Provide the support for global custom labels.