Hi! Please see the discussion in https://lists.apache.org/thread/6p5tk6obmk1qxf169so498z4vk8cg969 and the ticket: https://issues.apache.org/jira/browse/FLINK-33548
We should follow the approach outlined there. If you are interested you are welcome to pick up the operator ticket. Unfortunately your PR can be a large unexpected change to existing users so we should not add it. Cheers, Gyula On Tue, Dec 5, 2023 at 9:05 AM 苏超腾 <richardsuc...@gmail.com> wrote: > Hello everyone, > > I've encountered an issue while using flink kubernetes native, Despite > setting resource limits in the pod template, it appears that these limits > and requests are not considered during JobManager(JM) and TaskManager (TM) > pod deployment. > > I find the a issue had opened in jira FLINK-24150, which introduced > almost the same questions that I encountered. > > I agrees that if user had provided pod templates, we should put priority > on it higher than flink calculated from configuration. > > But this need some discussion in our community, because it related some > scenarios: > If I want to create a pod with Graranted QoS and want the memory of the > Flink main container to be larger than the process size of Flink, I cannot > directly modify podTemplate (although we can use limit factor, this will > cause the QoS to change from Graranted to Burstable) > If I want to create a pod with Burstable QoS, I don't want to use limit > actor and want to directly configure the request to be 50% of the limit, > which cannot be modified. > In order to meet these scenarios, I had committed a pull request > https://github.com/apache/flink/pull/23872 > > This code is very simple and just need someone to review, this pr can be > cherry pick to other old version, which will be helpful. > > > I would appreciate any feedback on this. > > Thank you for your time and contributions to the Flink project. > > Thank you, > chaoran.su
