You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "syepes (via GitHub)" <gi...@apache.org> on 2025/11/02 08:48:32 UTC

Re: [PR] [FLINK-29110] Use StatefulSet instead of Deployment to deploy JM and … [flink-kubernetes-operator]

syepes commented on PR #357:
URL: https://github.com/apache/flink-kubernetes-operator/pull/357#issuecomment-3477664414

   I've recently started using this operator as well, and I also found it a bit odd that the Job Manager runs as a Deployment rather than a StatefulSet on Kubernetes.
   
   I agree that using Deployment for the TaskManagers makes sense since they are mostly stateless, but Job Managers are stateful. Using a StatefulSet for them would make PVC management easier and would also align better with Kubernetes best practices.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org