Skip to content

K8 operator: Update supported KurrentDB versions to v26#957

Open
stktung wants to merge 7 commits intomasterfrom
k8-op-update-supported-version
Open

K8 operator: Update supported KurrentDB versions to v26#957
stktung wants to merge 7 commits intomasterfrom
k8-op-update-supported-version

Conversation

@stktung
Copy link
Contributor

@stktung stktung commented Feb 16, 2026

Description

Page previews

@stktung stktung requested a review from a team as a code owner February 16, 2026 07:22
@github-actions
Copy link

github-actions bot commented Feb 16, 2026

Docs build

@github-actions
Copy link

Docs build

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Feb 16, 2026

Deploying documentation with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8703e53
Status: ✅  Deploy successful!
Preview URL: https://c5c55b54.documentation-21k.pages.dev
Branch Preview URL: https://k8-op-update-supported-versi.documentation-21k.pages.dev

View logs

@stktung stktung changed the title Update supported KurrentDB versions in README K8 operator: Update supported KurrentDB versions to v26 Feb 16, 2026
@alexeyzimarev
Copy link
Member

/review

@qodo-code-review
Copy link
Contributor

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Version Wording

The supported versions list mixes major/minor patterns (e.g., v25.x, v24.x) while v26 is listed as v26.0. Consider whether this should be v26.x for consistency and to avoid implying only 26.0 is supported.

## Supported KurrentDB Versions

The Operator supports running the following major versions of KurrentDB:
- v26.0
- v25.x
- v24.x
Doc Consistency

The text says “KurrentDB version 26 will be used” while the manifests pin a specific patch version (26.0.1). Consider aligning wording and examples (either keep examples generic like 26.x or make the text explicitly mention the pinned patch version).

- The database will be deployed in the `kurrent` namespace with the name `kurrentdb-cluster`
- Security is not enabled
- KurrentDB version 26 will be used
- 1 vCPU will be requested as the minimum (upper bound is unlimited)
- 1 GB of memory will be used
- 512 MB of storage will be allocated for the data disk
- The KurrentDB instance that is provisioned will be exposed as `kurrentdb-0.kurrent.test`

```yaml
apiVersion: kubernetes.kurrent.io/v1
kind: KurrentDB
metadata:
  name: kurrentdb-cluster
  namespace: kurrent
spec:
  replicas: 1
  image: docker.kurrent.io/kurrent-latest/kurrentdb:26.0.1
  resources:
Image Tag Updates

The examples update image tags to 26.0.1; double-check that this tag exists/published in the referenced registry and that all related operator docs/examples consistently reference the intended 26.x tag strategy (pinned vs floating).

  namespace: kurrent
spec:
  replicas: 1
  image: docker.kurrent.io/kurrent-latest/kurrentdb:26.0.1
  sourceBackup: kurrentdb-cluster-backup
  resources:
    requests:

@github-actions
Copy link

github-actions bot commented Feb 16, 2026

Docs build

@github-actions
Copy link

Docs build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants