-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
🌱Build the kubebuilder binary before and use it to regenerate the helm chart #4420
Conversation
Hi @monteiro-renato. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
@@ -89,9 +89,9 @@ generate-docs: ## Update/generate the docs | |||
./hack/docs/generate.sh | |||
|
|||
.PHONY: generate-charts | |||
generate-charts: ## Re-generate the helm chart testdata only | |||
generate-charts: build ## Re-generate the helm chart testdata only |
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.
So we need to call here make install instead right?
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.
Personally, I never actually use make install
, I find it too intrusive.
I prefer to use the binary in the bin folder.
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.
Ok. So, based on your POV, we might need to leave it as it is.
We recommend using Make Install in all places.
However, it has contributors do not like it, they will prefer as you to build
So, leaving it as it is allows people to have a choice
WDYT?
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.
In my opinion, it makes sense to use the kubebuilder version built from main since this is regenerating data in the ./testdata directory.
The make generate
command, and more specifically, the make generate-testdata
command, calls the script in https://github.com/kubernetes-sigs/kubebuilder/blob/master/test/testdata/generate.sh#L123C1-L123C9 which is also building kubebuilder (https://github.com/kubernetes-sigs/kubebuilder/blob/master/test/common.sh#L108-L113) and putting it in a tmp directory instead of relying on the locally installed version.
But feel free to close the PR if you thing it's best to leave it as is.
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.
Your argumentation is fair enough 👍
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.
/ok-to-test
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86, monteiro-renato 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 believe this way is better? Specially now that the helm plugin is not yet available in any released version of kubebuilder?
For me, it also makes testing easier as I can make changes to the code and see it reflected in the generated chart without having to remember to
make install
beforehand.