Skip to content
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

backports/v1.0/2131 #2136

Merged
merged 2 commits into from
Feb 23, 2024
Merged

backports/v1.0/2131 #2136

merged 2 commits into from
Feb 23, 2024

Conversation

willfindlay
Copy link
Contributor

Backport of #2131.

Containerize the CRD generation workflow to resolve a version consistency issue we encountered. Rename the generate and codegen targets to disambiguate them.

[upstream commit: 5df7458]

We encountered some version-specific differences related to golang tooling which impact
the resulting CRD generation from make generate. To solve this problem, let's containerize
the CRD generation workflow so that we can get consistent output through consistent
tooling. while we're at it, rename the generate target to crds to disambiguate it from
protobuf code generation. We keep the old generate target around as an alias for backward
compatibility.

Signed-off-by: William Findlay <will@isovalent.com>
[upstream commit: 6df735d]

Now that we have renamed the generate target to crds, it makes sense to also rename to
codegen target to make it more clear that it specifically refers to protobuf codegen. Just
as with make generate, we keep the old codegen target around to use as an alias for
backward compatbility. We also remove the original protogen dockerfile as it is no longer
needed. Instead, we can simply use the base cilium-builder image.

Signed-off-by: William Findlay <will@isovalent.com>
@willfindlay willfindlay added the release-note/misc This PR makes changes that have no direct user impact. label Feb 22, 2024
@willfindlay willfindlay requested review from mtardy and a team as code owners February 22, 2024 18:53
@willfindlay
Copy link
Contributor Author

Links checker failure seems unrelated to me. @mtardy happen to know what's up? Seems to be failing consistently if I re-run it but I don't see how this PR could have caused it.

@willfindlay willfindlay merged commit c4ac46d into v1.0 Feb 23, 2024
30 of 31 checks passed
@willfindlay willfindlay deleted the backports/v1.0/2131 branch February 23, 2024 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants