Docs: sync upstream clickhouse-operator docs updates#49
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Syncs the latest
/docscontent fromclickhouse/clickhouse-operatorintoproducts/kubernetes-operator/so the Mintlify site reflects upstream.Sourced from upstream commit
963ff9a("feat: apply reload-safe config changes without restart"). cc @scanhex12 for review as the original author of the upstream docs changes.Changes
products/kubernetes-operator/guides/configuration.mdx— copied from upstreamproducts/kubernetes-operator/guides/introduction.mdx— copied from upstreamproducts/kubernetes-operator/install/olm.mdx— copied from upstreamproducts/kubernetes-operator/reference/api-reference.mdx— copied from upstreamPer instructions, files were copied verbatim from upstream — no edits to fix downstream issues.
Files in upstream
/docsthat are intentionally not synced (dev tooling / not part of the Mintlify site):README.md,development.md,navigation.json,styles/,templates/.Conflicts / issues to fix upstream before merging
mint broken-linksreports 5 broken links introduced by this sync. These are upstream issues — the upstream docs link to ClickHouse docs paths without the/coreprefix that the Mintlify site uses for the core ClickHouse product. They should be fixed inclickhouse/clickhouse-operatorupstream and re-synced.In
products/kubernetes-operator/guides/configuration.mdx:/concepts/features/configuration/server-config/configuration-files#example-1→ should be/core/concepts/.../reference/settings/server-settings/settings→ should be/core/reference/.../concepts/features/configuration/settings/settings-users→ should be/core/concepts/...In
products/kubernetes-operator/guides/introduction.mdx:/reference/engines/database-engines/replicated(×2) → should be/core/reference/...mint validatepasses. The remaining broken link reported bymint broken-links(integrations/language-clients/java/jdbc.mdx→/integrations/sql-clients/sql-console) is pre-existing and unrelated to this sync.