-
Notifications
You must be signed in to change notification settings - Fork 17
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
Flatten the repository structure #164
Comments
❤️ |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Is your feature request related to a problem? Please describe:
The repository is making extensive use of kustomize, which at some places makes it harder than necessary to understand how everything comes together.
Describe the solution you'd like:
We should try to flatten the repo structure and avoid unnecessary deeply nested directory structures and workarounds to Kustomize's behavior where possible.
E.g. it would be nice to flatten instancetypes from this
to this:
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional context:
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: