[UseCase|Inspiration] OneChart similarity of application

[leleobhz]

Hello!

I used OneChart as a chart-to-easy-deploy-my-old-compose-apps and since the project got read-only, I'm searching for a mantained substitute. Application may comes in this place.

But OneChart does have some features (It abstracts the Ingress - as example) that may be a source of inspiration to Application. For my deployments I'll check if Application may feet, but I think bring this to you may be useful somewhat.

Thanks!

[beiertu-mms]

Thank you @leleobhz for considering using our charts.
Please feel free to open any issues or discussions when encountering a problem.

[heubeck]

@leleobhz just like to follow up - have you identified concrete needs of yours in the application chart?

we decided to not add ingress in the past because in your practice, there's multiple applications/components addressed by a single ingress resource - but that's not set in stone.

[leleobhz]

Hello @heubeck !

For sake of maintenability I initially forked OneChart with a lot of backports from other repositories. The result can be seen at https://github.com/ZenithTecnologia/onechart (And diff on gimlet-io/onechart@master...ZenithTecnologia:onechart:main ). Reason I did this is because I used OneChart before know this repo and I have some production environments using this today.

That said, Storage and Ingress/API Gateway abstraction is a very wellcome addition, since it's a pain to handwrite these manifests. Also I miss on OneChart the ability to place more than one container (initContainer is possible).

I have in mind simpler statful applications "with anubis" (As an example): Storage abstraction, Ingress/Gateway abstraction, Service abstraction, easy deployment/sts declarations and some sec support for the future.

I consider OneChart not maintenable on my fork because I'm "just one" and templating can be very demanding to do alone and this is the reason I tried to found something else. Old mantainer replaced OneChart by AI but I do beleve controlling manifests is more important and AI does not bring this at an acceptable level w/o same level of work to use something like your chart or even OneChart.

I even tried https://kube-composer.com/ but it does not handle even simpler storage/network scenarios, forcing me to write about 50% of some manifests onechart does not handle (As the example, multiple containers).

I can try contribute with something but I can't write a entire stack from 0. That said, I tried here to explain in words the kind of feature I think is good to simplify and standarize the deploy for almost everything that uses a docker-compose - as an example.