lhotari commented on issue #571:
URL:
https://github.com/apache/pulsar-helm-chart/issues/571#issuecomment-2668011332
> Ok thanks for your feedback. this means I can use the apachepulsar/pulsar
image to deploy pulsar and therefore use the lightest image. I was thinking
there might be scripts or something used in the pulsar-all image to instantiate
the cluster or do other configurations.
In most cases there won't be much benefit of using apachepulsar/pulsar if
pulsar-all gets used eventually since a k8s node will cache the pulled images.
Obviously there will be some benefit when the initial jobs start faster,
without downloading the full pulsar-all image. We should target eliminating the
use of pulsar-all image.
Even when using Pulsar Functions and Pulsar IO connectors, most users could
upload the connectors they use separately. It's also possible to make the
cluster download from an external URL as long as the URL is whitelisted in the
configuration (`additionalEnabledConnectorUrlPatterns` and
`additionalEnabledFunctionsUrlPatterns` in `conf/functions_worker.yml`).
> I can also propose an apachepulsar/pulsar-all image without adding the
connectors.
For legacy reasons, I think a new name should be picked. I guess most users
would only need tiered-storage ("offloaders") in the image for a Pulsar cluster
in addition to the plain Pulsar image (which should be kept as small as
possible).
We could start publishing a new image with tiered-storage if that would be
sufficient.
Perhaps the name could be `apachepulsar/pulsar-cluster` so that we don't
limit it only for adding `tiered-storage` into the image.
I checked the tiered-storage modules and they are very large due to
duplicating unnecessary dependencies inside the nar files. A similar solution
as https://github.com/apache/pulsar/pull/9638 should be applied to the
tiered-storage nar files (using `provided` scope for dependencies available in
Pulsar).
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
