This message was deleted.

With the REST API, you will have to escape the customRuntimeOptions json like this:

"customRuntimeOptions": "{\"nodeSelectorLabels\":\"pulsar\",\"tolerations\":{\"key\":\"pulsar\",\"value\":\"true\",\"effect\":\"NoSchedule\",\"operator\":\"Equal\"}}"

alright thanks, right now Im not able to set these. I’ve followed the link that you’ve shared here.

Are you using

org.apache.pulsar.functions.runtime.kubernetes.BasicKubernetesManifestCustomizer

? And how did you set it?

I set it using a ConfigMap - @Affan?

@Alexander Preuß inside of the broker pod i manually edited

conf/functions-worker.yml

and added the line

runtimeCustomizerClassName:org.apache.pulsar.functions.runtime.kubernetes.KubernetesManifestCustomizer

@Affan If I remember correctly, the config yamls are only read when the broker is (re-)started, but if you manually edited it I believe restarting the broker will cause the yaml to be reset

@Alexander Preuß oh I see, the documentation suggested that I should edit the

conf/functions-worker.yml

what is the proper way to go about it?

That depends on how you deployed pulsar to kubernetes, if you are using the Apache Helm chart, I would expect there to be an option somewhere for overriding the values in that yaml

@Alexander Preuß Yes I'm using apache pulsar helm chart however, the values.yaml line 798-806 give no way to change this under the function-worker component.

You might be able to set these properties through the brokers ConfigMap: https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/broker-configmap.yaml#L148 but I’m not super familiar with the pulsar helm chart. Maybe someone else can confirm