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

✨Separate CRDs in the Helm chart #1920

Merged
merged 3 commits into from
Mar 20, 2024
Merged

Conversation

francostellari
Copy link
Contributor

@francostellari francostellari commented Mar 19, 2024

Summary

Move CRDs to the chart crds/ folder to let Helm install them before applying the template

Related issue(s)

Fixes #

Signed-off-by: francostellari <fstellari@gmail.com>
@kcp-ci-bot kcp-ci-bot added dco-signoff: yes Indicates the PR's author has signed the DCO. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 19, 2024
Signed-off-by: francostellari <fstellari@gmail.com>
@@ -15,7 +15,7 @@ namePrefix: kubestellar-
# someName: someValue

resources:
- ../crd
# - ../crd
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What was this kustomization accomplishing?

If we are no longer going to use that, perhaps it should be deleted?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing this line prevents the CRDs from being injected into the chart template yaml.
When doing the same in kubefkex and otp, we commented the line instead of completely removing it.
I can remove it if you prefer

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better to just remove it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my own testing and analysis, it appears that this particular line was accomplishing nothing. It is a bit of generic infrastructure inserted by kubebuilder, but it never made a difference in this repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok done

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand correctly,

cp config/crd/bases/* pkg/crd/files
is also saying --- and relying on the fact that --- this repo is not using any kustomize functionality for its CRDs. @pdettori , have I got this right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikeSpreitzer correct, at least for the CRD there is currently no kustomization done.

Signed-off-by: francostellari <fstellari@gmail.com>
Copy link
Contributor

@MikeSpreitzer MikeSpreitzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2024
@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 9b155ae16b8775dadcacdfea95e74fbafe885820

@MikeSpreitzer
Copy link
Contributor

/approve
Thanks!

@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MikeSpreitzer

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2024
@kcp-ci-bot kcp-ci-bot merged commit 424d266 into kubestellar:main Mar 20, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants