Repository navigation
Conversation
…blished The README instructs adding https://apache.github.io/druid-operator, but that repository has never been published (the gh-pages index.yaml is empty and the helm-chart publish workflow has not been run), so the documented commands fail. Meanwhile the chart's previous home, charts.datainfra.io, is a lapsed domain no longer under the project's control. Keep the hosted-repository instructions as the intended flow, but document the currently working installation from the repository's chart/ directory and warn against the lapsed domain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README instructs
helm repo add apache-druid https://apache.github.io/druid-operator, but that repository has never been published: thegh-pagesindex.yamlis empty (entries: {}), thehelm-chart.ymlworkflow (manualworkflow_dispatch) appears never to have been run withpublish=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.