feat: Helm Chart for Kubernetes Deployment

[GopalGupta1805]

Is there an existing feature or issue for this?

• I have searched the existing issues

Expected feature

Creation of Kubernetes Helm Chart for reNgine.

I am creating a Kubernetes Helm Chart for reNgine but I am facing issues as follows:

1. No image is available for celery, celery-beat & web. I need to build the image every time.
2. The staticfiles are mounted in nginx proxy and are routed through nginx, causing an issue when I am trying to route it via nginx-ingress. It's supposed to be redirected by the web image instead of nginx proxy image.

Alternative solutions

No response

Anything else?

No response

[github-actions]

Hey @GopalGupta1805! 🚀 Thanks for this exciting feature idea!

We love seeing fresh concepts that could take reNgine to the next level. 🌟

To help us understand your vision better, could you:

📝 Provide a detailed description of the feature
🎯 Explain the problem it solves or the value it adds
💡 Share any implementation ideas you might have

Your input is invaluable in shaping the future of reNgine. Let's innovate together! 💪

[0xtejas]

Hello,

I thought of setting up k8s but I'm unfamiliar with Helm charts as I'm still learning things.

However to answer your question you need not build web everytime you can just pull docker pull yogeshojha/rengine as it is web image.

What is the issue that you are facing when having Nginx-Ingress controller? I can't imagine any issues. Current setup in the docker looks fine to me.

[0xtejas]

@yogeshojha
It looks like the Celery and Celery-Beat images are custom-built. Given that this is a multi-service Docker application where these services are interdependent, it would make sense to push all the custom-built images to the registry, not just the web app.

Since Nginx, Celery, Celery-Beat, and the Django app all work together, there's little benefit in only pushing the Django (web) image if the other custom images (like Celery) aren't also available in the registry. This could lead to missing components or inconsistencies when deploying to other environments.

Let me know if I've misunderstood anything, but I believe it's important to ensure all the relevant custom images are pushed to the registry for seamless deployment.

[0xtejas]

This issue feat request is similar to #1458 , and is addressed in the PR #1457