kunjbosamiaFalkonry commented on issue #394:
URL:
https://github.com/apache/pulsar-helm-chart/issues/394#issuecomment-2071520742
> 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 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](https://pulsar.apache.org/docs/next/functions-cli/#yaml-configurations-for-pulsar-functions).
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`
--
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: commits-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
