Hello all, I'm trying to figure out how to setup

taskmanager.numOfTaskSlots

via the Flink Kubenetes Operator. I'm using the operator version 1.13.0 and Flink 1.20.3. While the configmap generated by the operator correctly reflects the set value (

'3'

in my case). It looks like during the actual taskmanager startup process, it resolves

taskmanager.numOfTaskSlots=1

as a Dynamic configuration property, which overrides the value at runtime. Has anyone successfully set a value larger than 1 in K8s in the past?

I’ll go digging around. I’m almost certain that I’ve used values greater than 1 for quite a few jobs (and I almost exclusively use the K8s operator). I’ll report back once I have a chance to look.

Could it be a typo, @Idan Sheinberg? In my charts this defined like so (notice the uppercase 'M' in

taskManager

): taskManager: numberOfTaskSlots: 2 EDIT: never mind me, we have a layer of Go templating that transform the above mentioned

taskManager

into the documented lowercase

taskmanager

. This is the effective chart:

flinkConfiguration:
    taskmanager.numberOfTaskSlots: "2"

And it works fine for us. We're running a slightly outdated version of the Operator (1.10.0)

Thank you for responding @Andreas Bube @Rion Williams. We are using

taskManager.numberOfTaskSlots: "3"

. However, I now see it should be

taskmanager

, not

taskManager

. I'll check and let you know

Great. Happy to hear you managed to solve it