test: add openshift e2e smoke test#202
Merged
Merged
Conversation
GrigoryPervakov
force-pushed
the
okd-test
branch
14 times, most recently
from
446f552 to
dab3ace
Compare
GrigoryPervakov
force-pushed
the
okd-test
branch
5 times, most recently
from
51b9924 to
d777275
Compare
GrigoryPervakov
force-pushed
the
okd-test
branch
3 times, most recently
from
8d17859 to
da91f1f
Compare
Adds an OpenShift compatibility smoke test driven from a self-hosted runner that hosts a long-lived OKD single-node cluster. The test subscribes to the fast-v0 channel of the operator's OLM catalog, waits for the CSV to succeed, then drives a Keeper + ClickHouse deployment in a dedicated test namespace. Operator-side: keeper and clickhouse now mount an emptyDir at the data path when neither DataVolumeClaimSpec nor a user-supplied mount covers it. Lets the default install work under OpenShift's arbitrary-uid SCC + readOnlyRootFilesystem. Workflows: - openshift-compatibility.yaml: runs after the main-branch artifact publish workflow finishes, plus workflow_dispatch for manual reruns against any branch. - openshift-runner-rebuild.yaml: weekly cron destroys + reinstalls the long-lived cluster so kubelet certs and OS state stay fresh. Runner image + cleanup/rebuild scripts live in a separate repo (github.com/ClickHouse/clickhouse-operator-olm-runner).
GrigoryPervakov
force-pushed
the
okd-test
branch
from
da91f1f to
5b12ab1
Compare
|
Docs PR opened: ClickHouse/mintlify-docs-dev#173 Synced upstream clickhouse-operator docs, adding a new monitoring guide and updating configuration, introduction, overview, and API reference pages. |
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.
Why
Need to verify OpenShift compatibility
What
Add a special OpenShift e2e test against the pre-provided OKD cluster.
ClickHouse images have data dirs created with user 101, but OpenShift randomizes UID of the service, so now the operator mounts an emptyDir to match the data dir owner