feat: k8s deployment for reNgine

[0xtejas]

Is there an existing feature or issue for this?

• [X] I have searched the existing issues

Expected feature

Support K8s configuration for reNgine

Alternative solutions

No response

Anything else?

No response

[github-actions[bot]]

Hey @0xtejas! 🚀 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]

I have a PR #1457 and I'm looking for some additional help to get it ready.

I need additional hands on this to improvise a few more things:

• [ ] Add Ingress
• [ ] Support SSL from LetsEncrypt or Cert Manager services provided by Cloud
• [ ] Current setup works for Digital Ocean. Native block storage provided by the PVCs doesn't support ReadWriteMany. Will have to test if the current configuration works on other cloud providers that use OpenEBS NFS Provisioner. I had to install OpenEBS NFS Provisioner on the Digital Ocean's k8s marketplace.
• [ ] Fix the issue when routing with a domain name, I assume this will be resolved by solving the first two issues. Currently, I can view reNgine using https://IP, not the domain name.
• [ ] Additionally, make some changes such that the DB works in master-slave or another concept to make use of the replicas that can be created using stateful sets.
• [ ] Support user account creation upon web pod deployment.

[pythonSB]

Celery itself supports distribution, which can be achieved with minor modifications