-
Notifications
You must be signed in to change notification settings - Fork 67
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
feat: Add podLabels to Helm chart #1054
Conversation
Hi @bjw-s. Thanks for your PR. I'm waiting for a backube member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Bernd Schorgers <me@bjw-s.dev>
helm/volsync/Chart.yaml
Outdated
@@ -66,7 +66,7 @@ kubeVersion: "^1.20.0-0" | |||
# This is the chart version. This version number should be incremented each time | |||
# you make changes to the chart and its templates, including the app version. | |||
# Versions are expected to follow Semantic Versioning (https://semver.org/) | |||
version: "0.8.0" |
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.
Can you roll back this change? I don't want to modify the default version to v0.9.0 at this point
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.
I'm fine doing that, I merely changed it because of that instruction This version number should be incremented each time you make changes to the chart
following semVer.
I will submit a PR soon.
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.
I've removed the chart version bump.
Looks like some formatter fixes were applied automatically, are they OK to keep?
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.
Thanks for that - you're right normally we would update the version, but we'll do it at the same time when we make a v0.9 release. I think the formatter fixes are probably ok.
Signed-off-by: Bernd Schorgers <me@bjw-s.dev>
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
@JohnStrunk are you ok with this update to the helm charts? |
Looks fine to me. Of note: this doesn't cover the mover pods, just the VolSync controller. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bjw-s, JohnStrunk The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I would love to be able to set labels on the mover pods as well (to more easily target them with networkPolicies for example), but that would require changes to the Go code. I haven't dared to dig in to that yet 😅 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1054 +/- ##
=======================================
+ Coverage 66.9% 67.0% +0.1%
=======================================
Files 55 55
Lines 7080 7080
=======================================
+ Hits 4739 4748 +9
+ Misses 2061 2055 -6
+ Partials 280 277 -3 |
@bjw-s FYI: We've just made a change for #707 which also included the ability to set podLabels for a mover. See PR: #1072 |
/lgtm |
@tesshuflower I'm having some trouble figuring out where the test is failing exactly (and how it can be failing based on my changes 😅). Can you perhaps offer some guidance? |
Most likely not due to your change, sometimes we're still getting intermittent failures as these test clusters are pretty resource constrained. /retest |
Describe what this PR does
It is already possible to define Pod annotations on the volsync controller Deployment. This PR makes it possible to set Pod labels as well.
Is there anything that requires special attention?
Related issues: