Gautam Prajapati

@nolar Thank you so much for the detailed response. > Yes, using either daemons or timers is the right way to do this task. They were actually designed for the...

> Is this ready for review? Yes, CRD can be reviewed, but, before that I'm thinking to include a detailed documentation as well so that it's easy to review. It's...

@thedrow I had added documentation for the CRD in a structured format. You could start by reviewing it and suggest any changes if needed. I'm working on modeling spec received...

> the CRD.yaml file is too big. Yes. It includes support for lots of standard Kubernetes resources/objects specification like volumes, volumeMounts, envs, init containers etc. that are commonly used while...

@auvipy @thedrow this is ready for review

> > @auvipy @thedrow this is ready for review > > I'll probably only have time to review this after 5.1 is released. Thanks, Sorry for the slow progress from...

I devote 20% of my time(Every Friday + Some part of the weekend) to this project to move things in a consistent way. Any contributions/help is welcome

A somewhat detailed task list for the first release - - [x] Write a production-ready CRD for the cluster (https://github.com/celery/Celery-Kubernetes-Operator/pull/15) - [x] Explore Kind for bootstrapping local Kubernetes cluster and...

Is there any progress/update on this? I was wondering if Celery would like to see the adopt operator pattern in addition to the Helm chart. Let me know if I...

> @brainbreaker If you have experience with Celery and you need that kind of thing at work I suggest you help us. > We're working on the next generation of...