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
Update controller tools v0.6.2 #17596
Update controller tools v0.6.2 #17596
Conversation
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 separating this out and taking care of the controller-tools update. LGTM.
@jrajahalme needs rebase |
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.
The new cmdrefs for completion seem a bit unnecessary but I'm assuming that it's all just part of the tool-based autogeneration so sure 👍 LGTM from docs-structure perspective.
The ginkgo changes looked pretty confusing at first glance so I'm assuming the other reviewers took a closer look.
9c68daf
to
f6b6573
Compare
We'll have to see the CI. runs to know if the Ginkgo changes are complete and if our test suite is compatible with this Ginkgo version... 🤞 |
/test Job 'Cilium-PR-K8s-GKE' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment Job 'Cilium-PR-K8s-1.21-kernel-4.9' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
All the test fails seem wholly unrelated to these changes, which are:
Based on the above I'm labeling this PR as ready-to-merge. |
/mlh new-flake Cilium-PR-K8s-GKE 👍 created #17617 |
/mlh new-flake Cilium-PR-K8s-1.21-kernel-4.9 👍 created #17618 |
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.
Code changes LGTM.
Shouldn't we wait for other reviewers to approve? 🤔 Also re: flakes => I think we should really try to either block or disable when that happens /cc @twpayne |
@nbusseneau All requested team reviews are already covered. Nathan and Robin's reviews were required for cilium/kubernetes and cilium/vendor respectively. Those two teams are already covered by Chris and André. |
The following controller-tools update pulls in a new ginkgo version with a deferred Describe() change that is incompatible with the Cilium Ginkgo suite handling of scopes. Separate this change and fix to this commit to make it clear what is going on. To properly deal with deferred Describe() handling of Ginkgo, we also need to defer the scope handling by moving it to the function body called by Ginkgo. Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
Update controller tools to get object-level support for unknown fields. This is needed for Envoy CRDs. Still using the fork at https://github.com/christarazi/controller-tools/tree/v0.6.2 test: Fix ginkgo breakage due to new version Documentation: Add completion files due to spf13/cobra update Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
f6b6573
to
5587b15
Compare
@joamaki asked for a rebase & retest, so here we go :-) |
/test Job 'Cilium-PR-K8s-1.19-kernel-5.4' hit: #17353 (90.54% similarity) |
Update controller-tools to v0.6.2 to gain support for opaque json in k8s custom resources. This is needed for including Envoy resources in the upcoming Cilium Envoy Config CRD.
This update pulled in a Ginkgo update which required some CI updates. These are separated out into a commit of their own to make reviewing easier.