Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open points for Kubernetes operator #30

Open
4 tasks
gautamp8 opened this issue Dec 19, 2020 · 3 comments
Open
4 tasks

Open points for Kubernetes operator #30

gautamp8 opened this issue Dec 19, 2020 · 3 comments

Comments

@gautamp8
Copy link
Collaborator

gautamp8 commented Dec 19, 2020

#29 describes the first draft of Celery Kubernetes operator. This issue describes some of the open points for the implementation that need exploration.

  • Add detailed documentation for CRD spec for Celery - An exhaustive list of parameters to be supported and their use-cases
  • Deep dive into autoscaling implementation and parameters on which it should be triggered
  • Deployment and distribution approach to be able to install the preferred broker + results backend along with the operator
  • Any other use-cases the operator should support
@thedrow
Copy link
Member

thedrow commented Feb 17, 2021

Are you planning to complete this CEP?
Is there anything more you need to know?

@gautamp8
Copy link
Collaborator Author

Are you planning to complete this CEP?

Yes. I'm continuing on the repository itself. Here's an Issue outlining what I'm planning for the first release.

As I gain more clarity researching and writing code, I'll keep modifying this proposal to reflect the updates.

@elonzh
Copy link

elonzh commented Jun 24, 2021

I don't see any special capability for celery, introducing a new controller and CRD is actually increasing the ops burden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants