merlimat commented on PR #367:
URL:
https://github.com/apache/pulsar-helm-chart/pull/367#issuecomment-1630409999
@eolivelli @lhotari The current problems with the Helm chart are not
something that can be easily fixed, unless significant investment is committed
to the effort.
In my view:
* The Helm chart is lagging behind Pulsar releases with no ETAs on whether
the "current" release will be available
* Many of the feature combinations are not working out of the box, because
of changes in K8S APIS, compatibility with different cloud providers, etc..
* The result is that, currently, it's very difficult to get anything other
than a trivial basic clusters working out of the box.
As per the source of these issues, I think it comes that mostly everyone
uses different means to deploy Pulsar in Kubernetes (eg: operators or forks of
the original Helm chart), therefore this Helm Chart is practically untested by
most of the people working on the project.
For a user, though, we are promising that this Helm chart is the best
preferred way to deploy Pulsar in Kubernetes, while in fact it does not work
out of the box for the majority of the users (as you can see from the number of
people getting stuck and asking questions in Slack).
So, again in my view, there are 2 options:
1. Set the expectations on the "real" status of this Helm chart
2. Invest significant resources to make it work well, in the way users
would expect from an "officially supported" component.
Is there anyone who has the bandwidth to commit for making (2) happen?
--
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]
