customRuntimeOptions in "Creates a new Pulsar Source in cluster mode" API call in source connector doesn't add nodeselectors & tolerations about pulsar-helm-chart HOT 3 OPEN

Related to #382

from pulsar-helm-chart.

Related to #382

In this issue , you suggested to configure things by passing values to broker's config map. which i did

PF_runtimeCustomizerClassName: "org.apache.pulsar.functions.runtime.kubernetes.BasicKubernetesManifestCustomizer"
PF_runtimeCustomizerConfig_nodeSelectorLabels_test: value

based on this configuration , this will add nodeSelectors test:value to all the functions which will be deployed. Which is correct its the default nodeSelector. But I want different nodeSelector for different functions which I deploy. So I should pass ": "customRuntimeOptions": "{\"nodeSelectorLabels\":{\"customLabel\":\"value\"}" Passing it as string because type of customRuntimeOptions is string which is mentioned here.
I am getting this error when I am paassing customRuntimeOptions when creating a pulsar function ->

{"reason":"Function my-test-function cannot be admitted:- java.io.EOFException: End of input at line 1 column 40 path $.nodeSelectorLabels"}

If I don't pass customRuntimeOptions while creating the function , it works fine and take the default node selector test:value

from pulsar-helm-chart.

But I want different nodeSelector for different functions which I deploy.

@kunjbosamiaFalkonry One possible approach would be to create your own customizer implementation. Currently there's not an easy way to get your custom classes into use. You need a custom overlay docker image with the jar file in /pulsar/lib . There's a feature request to add init container support that could copy the jar file to /pulsar/lib when the pod starts. That's #491 / #240 . This is an open source project and contributions are more than welcome to improve Apache Pulsar Helm chart.

from pulsar-helm-chart.