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
lint: Add --kube-version flag to set capabilities and deprecation rules #10677
Conversation
caee60c
to
0334156
Compare
ping @antoinedeschenes |
0334156
to
f644f4c
Compare
@yxxhero Just reversed All and Templates signatures to the original, added new functions in parallel. |
ee46042
to
7e4445f
Compare
pign @yxxhero |
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.
Nice. This is what I originally had hoped to do when I added the upstream deprecation library. Thanks!
@joejulian Awesome, do you need a rebase? |
Not according to GitHub |
@yxxhero I don't like to nag, but this PR adds something super useful for us, and has been waiting for some time |
@pete-woods @yxxhero and I are just triage maintainers. You need a core maintainer to review. |
@joejulian me too. |
Ah. Didn't appreciate that - apologies |
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 this PR. I've long wanted this feature and am excited for it to land.
I found one minor issue that shows up for SDK consumers. Should be a quick fix if you could please make the change. Otherwise it looks good to me.
@antoinedeschenes can you make the one small change or should someone else make it? |
Anything missing? |
faa3237
to
46e3886
Compare
Any updates? |
Tested this and it works for me. I wish we could make it an error if it's past the unavailable deadline, but that would be a breaking change, I guess, and outside the scope of this PR. |
Any timeframe in mind? |
Note, I fixed a merge conflict caused by #12688 where |
Since my commit should not have made major changes to cause the failed test run, I checked out the commit before it and ran the test suite there. I get the same error of...
This is for commit 46e3886. This is because the internal k8s version is set to 1.20 which is what's used for the testing. So the I'm not sure how this test ever passed. The easy fix is to update |
Signed-off-by: Antoine Deschênes <antoine@antoinedeschenes.com>
2070b22
to
869c1d2
Compare
09bc834
to
af9c8d7
Compare
Signed-off-by: Joe Julian <me@joejulian.name>
af9c8d7
to
6e5332e
Compare
This should have made it work: 869c1d2#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R107 But it broke a bunch of other golden images that have labels with the k8s version data. Rather than have to update the golden files with every client-go release, I reverted the addition of ldflags on the test and switched the expected golden image to the old k8s one. |
sorry for my force-pushes. I neglected to sign my commit and am trying to help get this across the finish line for this release. |
Signed-off-by: Antoine Deschênes antoine@antoinedeschenes.com
What this PR does / why we need it:
closes #10664
Adds a
--kube-version
flag to thehelm lint
command, allowing to specify the Kubernetes version to use for the deprecation check warnings.There's a similar flag in the
helm template
command.Specific example of where this is useful:
helm lint --strict
is currently erroring out on HorizontalPodAutoscalerautoscaling/v2beta2
having to be replaced byautoscaling/v2
.autoscaling/v2
doesn't exist yet on Kubernetes 1.22.If applicable: