danc opened a new pull request, #31: URL: https://github.com/apache/druid-operator/pull/31
The README instructs `helm repo add apache-druid https://apache.github.io/druid-operator`, but that repository has never been published: the `gh-pages` `index.yaml` is empty (`entries: {}`), the `helm-chart.yml` workflow (manual `workflow_dispatch`) appears never to have been run with `publish=true`, and the repo has no tags or releases — so the documented commands fail for every user. This matters more than usual because the chart's previous home, `charts.datainfra.io`, is a lapsed domain no longer under the project's control (it redirects to an unrelated third-party site — see datainfrahq/druid-operator#262), so right now there is no legitimate hosted helm repository for this operator anywhere. This PR keeps the hosted-repository instructions as the intended flow, but documents the currently working installation from the repo's `chart/` directory and warns against adding the lapsed domain. Beyond this docs fix: could a maintainer run the Helm Chart workflow with `publish=true` (and ideally cut a tagged release)? That would make the documented flow real and give users a safe successor to the squatted repository. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
