-
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
🐛 fix: (helm/v1alpha1): Add missing prefixes in various k8s resources #4388
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. |
@@ -0,0 +1,1161 @@ | |||
--- |
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 understand that you added this to make it easier to review the changes, and it seems like an interesting approach.
However, it appears this was done manually. All the files generated under testdata are created using the shell script found at generate.sh. We cannot manually add or modify content in this directory. Instead, the logic for generating these files needs to be incorporated into the script. Also, the action that calls it will need to have helm installed. We check if the testdata is updated with the PR changes to allow get it merged see: https://github.com/kubernetes-sigs/kubebuilder/blob/master/.github/workflows/testdata.yml
Additionally, if we decide to include this change, we must ensure that the helm-install.yaml file is re-generated when running the Makefile target. This ensures consistency and alignment with the existing build and test automation processes.
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 think this change would need to be in an PR only for that.
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.
Hi @camilamacedo86,
The helm-install.yaml was indeed created manually but as I mentioned, it was only to make the review easier.
I've deleted it and squashed the commit now 👍.
I do think having a diff of the generated manifests makes it a lot easier to do reviews. It might be something to consider having as part of the normal pipeline.
Thank you for looking on this. See my comment: #4388 (comment) I think we need to split this PR, and for we get merged, we should have only one commit, ideally. |
5047219
to
cd5f6b1
Compare
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.
/lgtm
/approve
/ok-to-test
[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 |
Hey 👋
I've added missing prefixes to k8s resources (except for cert-manager ones)
I've added 4 commits so it's easier to review.
I will delete the helm-install.yaml file and squash the commits after the review.