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
{{ message }}
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
@tdaly61 I think this is actually an opportunity for us to actually get rid of helm completely. We could generate k8s deployment manifests from docker-compose files.
@elijah0kello , I think we could/should look at this because it may provide some simplifications but what we need to be careful about is not to introduce longer term issues. I can explain when we meet next week (or never hesitate to whatsapp me or ping me to meet at anytime) but helm absolutely has its place e.g. upgrades and chart versioning and enabling complex configuration etc so we don't want to throw it out when it is useful or indeed simplifies things BUT we also do not want to use it when it makes things more complicated than they need to be. For vNow for instance there are > 37K lines of helm values.yaml settings which is tragic for end users (vnext is < 1/10th of that total yaml lines) so absolutely lets look at this !! (sorry longer answer than you probably wanted BUT you raise an important question )
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, mojafos deploys a Mifos X with the old community app. We need to make it so that it deploys the latest stable release of the web app.
The text was updated successfully, but these errors were encountered: