Make Pinot's life cycle easy with [K8s Operator](https://www.redhat.com/en/blog/operators-101-your-auto-pilot-kubernetes-workloads) Let's target following: - Create and Destroy - Resize - Failover - Rolling upgrade - Backup and Restore

we can work on that to build k8s operators

and implement not only deployment

also include operations

I have some work on it. Let's collaborate

sounds good

Ya as a community mostly people will be interested in Phase IV and V

Insights, Scaling and Tuning

Agreed

it’s more day2day life

ya

@User FYI

this is amazing

Yes

For example ArgoCD has full Capability

I see what you mean now. this will be an amazing addition

I have used Spark and Flink the mostly..

@User has left the channel

Hello there! I hope you are doing well 🙂 Maybe I am too late to the party but I started a project for the Apache Pinot Kubernetes Operator 🚀 You can find it here: https://github.com/spaghettifunk/pinot-operator If you are interested in contributing or simply give feedback, it would be great 😄 Unless there is already a project like this and I failed to find it 😆

wow

Many thanks !!!!! I will take a look!

thanks 🙂 I really appreciate it

Is there work ongoing for a k8s operator?

Any guide to install pinot components in a k8s cluster with 3 nodes?

Do you know how many controller/broker/servers you need?

For prod quality, typically you need to have at least 2 pods per component and config node affinity to ensure all the pods are not scheduled on the same node

Is there any advice on the configuration of JVM ops and resource for a prod quality?

@Priyank Bagrecha has left the channel

Hello, is it possible to cut a new helm release with the 2 new changes that were merged in? Specifically this issue as it's causing issues when we have

readinessProbes

enabled. Thanks!