Repository navigation
ci: run cluster tests against KurrentDB 26.2 with a license key - #1297
Merged
Merged
Conversation
Multi-node KurrentDB 26.2 exits at startup without a license key. The key comes from the KURRENTDB_LICENSING__LICENSE_KEY secret and is passed to the cluster nodes; the cluster steps are skipped when it is not available, as on fork and Dependabot PRs. Each node activates a Keygen machine fingerprinted by MAC, CPU count and memory, and a stopped node does not deactivate it. The cluster MACs are pinned so runs reuse the same three machines instead of adding new ones. Single-node and fault-injection tests move to 26.2 as well; a single node needs no key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
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.
Multi-node KurrentDB 26.2 exits at startup without a license key. Kurrent issued a CI key for sec, stored as the
KURRENTDB_LICENSING__LICENSE_KEYrepository secret. It is passed to the three cluster nodes, and the cluster steps are skipped when the secret is unavailable, as on fork and Dependabot PRs.Each node activates a Keygen machine fingerprinted by MAC, CPU count and memory, and a stopped node does not deactivate it. The cluster MACs are pinned so runs reuse the same three machines; the key allows 100.
Single-node and fault-injection tests move to 26.2 as well; a single node needs no key. Locally the key goes in the git-ignored
.docker/.env, which docker compose reads.Verified locally: a three-node 26.2.2 cluster with the key validates the license on every node, and
tests / Cit / testpasses.