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

[Enhancement]: non-helm cndi_config[applications] #987

Open
1 task done
johnstonmatt opened this issue Aug 17, 2024 · 0 comments
Open
1 task done

[Enhancement]: non-helm cndi_config[applications] #987

johnstonmatt opened this issue Aug 17, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@johnstonmatt
Copy link
Contributor

Version

cndi v2.16.0
kubeseal v0.26.0
terraform v1.5.5

Please provide a summary of the enhancement you are proposing:

Generally CNDI Applications should always be helm-chart based. Helm is what the CNDI workflow has been engineered for. However some applications do not have helm charts available and we can still provide Templates by using the directory key in CNDI Applications.

Please provide the motivation or use case for this enhancement:

vitess.io is a mature and well-respected app that abandoned Helm. and we still want to provide a CNDI Template in cases like that.

How can we best workaround this issue so far?

cndi_config[cluster_manifests] could be used to specify an Application CRD manually, but this is a bit verbose and clunky.

How would you approach solving this problem within CNDI?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

1 participant