-
Notifications
You must be signed in to change notification settings - Fork 138
Closed
Labels
refinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.size/smallEstimated to be completed within ~2 daysEstimated to be completed within ~2 daystech-debtShort-term pain, long-term benefitShort-term pain, long-term benefit
Milestone
Description
As a maintainer and user of NGF
I want all generated CRDs to be placed in the standard 'config/crd' path as the source of truth
So that I can easily find the definitions for all CRDs in the project.
Acceptance
- Generated CRDs are located in the standard path
config/crd
and use it as the source of truth. - Helm charts are still able to utilize the generated CRDs from Helm's CRD directory using a symbolic link.
- NGF Manifests are still installable using the same method identified in our documentation.
Metadata
Metadata
Assignees
Labels
refinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.size/smallEstimated to be completed within ~2 daysEstimated to be completed within ~2 daystech-debtShort-term pain, long-term benefitShort-term pain, long-term benefit