Samuel Verstraete

Hi, Glad someone is finally looking at this issue. I've tried to rebase my changes on master but the conflict is *exactly* where i started changing code so i'm unsure...

> Thanks for the PR. Would it be possible to use the key `pulsar_metadata.nodeSelector` instead of `initialize_jobs.nodeSelector`? Please also add a placeholder in the default values.yaml with a comment documenting...

Does this change in anyway if we would be selfhosting? We are in the middle of moving off IIS... so if it would i might have to choose what scenario...

@drewnoakes any chance this can be picked up again? i'm willing to merge the conflicts and to follow up on any remarks you still have after review.

I'd call it a bug in the documentation then.

> @elangelo would you be interestedin picking up @janhoy idea of tweaking the AuthTool to handle the encoding? I'd prefer not to add another bash based tool, and stick to...

Make sure to whitelist the path of the token. `-Dsolr.allowPaths=/var/run/secrets/eks.amazonaws.com/serviceaccount/token` https://github.com/apache/solr-operator/issues/775

I'm not using the helm chart but i think `solrOptions.javaOpts` should be set. something like --set solrOptions.javaOpts="-Dsolr.allowPaths=/var/run/secrets/eks.amazonaws.com/serviceaccount/token" if you want to directly put it in the helm install command