Docs: sync upstream clickhouse-operator docs updates#209
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
arekborucki
approved these changes
Jun 17, 2026
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.
Summary
Syncs upstream clickhouse-operator#228 by @arekborucki, which documents
spec.clusterDomainin the Configuration guide.cc @arekborucki for review.
Changes
products/kubernetes-operator/guides/configuration.mdx— added new## Cluster domainsection between the PVC<Note>and## Pod configuration, copied verbatim from upstream.Context
Upstream commit:
024dd86— "docs: document spec.clusterDomain in configuration guide (#228)".Pre-existing upstream/downstream drift (not addressed here)
While syncing, I noticed the downstream copies under
products/kubernetes-operator/are behind upstreamdocs/on several files unrelated to PR #228. Flagging for awareness — these were not changed by this PR and were left alone:guides/configuration.mdx— beyond the cluster-domain section, downstream has different memory values in a resources example (256Mi/1Givs upstream512Mi/512Mi) and is missing the TLS cross-link and the entire## External Secretsection.guides/introduction.mdx,install/helm.mdx,install/kubectl.mdx,install/olm.mdx,overview.mdx,reference/api-reference.mdx— differ from upstream.guides/monitoring.mdx,guides/scaling.mdx,guides/tls.mdx— present upstream, missing downstream.Per instructions, only the actual change from PR #228 was synced; the rest should be reconciled upstream-first or via a separate dedicated sync.
Validation
mint validateandmint broken-linkstimed out in this environment on the full repo (unrelated to this change). The edit is a localized additive section that mirrors upstream exactly.Note
Low Risk
Documentation-only additive section mirroring upstream; no code or runtime behavior changes.
Overview
Adds a Cluster domain section to the ClickHouse Operator configuration guide, synced from upstream clickhouse-operator PR #228.
The new content explains that
spec.clusterDomain(defaultcluster.local) onClickHouseClusterandKeeperClustercontrols the DNS suffix used for pod FQDNs in generated ClickHouse config—replica hosts inremote_serversand Keeper coordination endpoints. It includes a YAML example and a note to override only when kubelet uses a non-default--cluster-domain, and to keep the same value on both cluster types to avoid DNS failures.Reviewed by Cursor Bugbot for commit c4242c1. Bugbot is set up for automated code reviews on this repo. Configure here.