Add ClickHouse client-shell manifest and usage docs - #128
Open
0xmc wants to merge 1 commit into
Open
Conversation
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.
Closes #127.
Adds an interactive
clickhouse-clientshell and its usage instructions so engineers can run ad-hoc queries against the o11y ClickHouse when operating or debugging the telemetry pipeline, without hand-rolling a client pod each time. The manifest provisions a shell pod ino11y-systemthat authenticates via client certs issued for theclickhouse-migrations-clientCN from theo11y-systemClusterIssuer, matching the TLS-only pattern the migrations job already uses. Usage is documented in the migration module's README, covering apply, exec into the client shell, and cleanup.The change has been sitting unmerged on
chore/clickhouse-client-shell(pushed, never PR'd); this brings it intomainand closes the tracking issue.Test plan:
kubectl apply -f ch-shell.yamlprovisions the shell pod ino11y-systemkubectl -n o11y-system exec -it ch-shell -- clickhouse-client ...connects over the secure port using the mounted client certssystemtables) without a passwordkubectl delete -f ch-shell.yamlcleans up the pod