You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 CNDIApplications
.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
The text was updated successfully, but these errors were encountered: