Skip to content

Commit cecb4b1

Browse files
authored
feat(opensearch)!: issue HTTP and Dashboards certificates from cert-manager (#2682)
## What this PR does The OpenSearch HTTP API (9200) and Dashboards (5601) already served TLS, from the operator's own private CA and with a SAN built from `cluster.local` while the credentials Secret advertised the release on the platform domain, so nothing a client was handed could verify. Both certificates now come from a per-release cert-manager CA in the tenant namespace, and the CA reaches tenants as a key-free trust anchor. - `tls.issuer` selects who issues the HTTP server certificate, `cert-manager` or `operator`, and is named for the issuer because TLS is served under both. Unset resolves from `external` (cert-manager for externally published services, the operator for cluster-internal); an explicit value always wins. - Renders a self-contained cert-manager chain in the tenant namespace: a self-signed Issuer, a CA Certificate, a CA Issuer, and two leaf Certificates, one for the HTTP API and one for Dashboards, each with the SANs of its own Service and the external hostname when `external: true`. Leaf keys are written as PKCS8, since the JVM loader rejects the PKCS1/SEC1 encoding cert-manager emits by default, and the CA subject is pinned so the operator's signature check accepts the chain. - The CA Secret is `<release>.http-ca`. The dot separates the chart-chosen suffix from release names, so no other release can produce that name; the two leaf Secrets stay hyphenated because none of the chart's suffixes is a tail of another. The operator's own transport CA remains at `<release>-ca` and is not touched. - Transport mTLS (9300) stays operator-managed (`transport.generate: true`, `perNode: true`). The security plugin requires it and the chart cannot turn it off. - `hack/e2e-chainsaw/opensearch/` runs the move on a cluster: it installs the app on the operator's HTTP listener, removes `tls.issuer` so it resolves from `external`, and asserts the cert-manager chain, the CR dropping `http.generate`, the admin certificate reissued under the chart CA, the StatefulSet rolling onto the three subPath mounts, the tenant anchor, and the certificate the endpoint actually presents to a client holding that anchor. ### Sysctl carrier and single-node rolls The E2E suite for this PR was red because the chart set `spec.general.setVMMaxMapCount: true`, which makes the operator prepend a privileged `init-sysctl` container to every OpenSearch pod. Tenant namespaces run at the cluster's default PodSecurity level, baseline on Talos, so admission refused the container and the StatefulSet never produced a pod (#4131). The carrier for the sysctl is now on main: #4152 added a DaemonSet to the `opensearch-operator` package that raises `vm.max_map_count` to a floor of 262144 on every node, from a namespace the platform labels privileged. This branch is rebased onto that main and sets the flag to an explicit `false`, with a template comment saying why and a unit test pinning it, so a release no longer asks the operator for a container admission refuses. The value stays with the DaemonSet until the node contract carries it (#4144); the DaemonSet's own template comment, which said the chart still asks, now says it does not. Three more things came out of the same pass. The chart asked the operator to drain data nodes before every rolling restart, and with a single data node the drain never finishes: at v2.8.0 `PreparePodForDelete` excludes the node from allocation and then waits for it to hold no shards, which the only data node can never satisfy, so a one-replica release could not roll for a version bump or for the certificate move this PR relies on. The chart now drains only when a second data node exists, pinned both ways in the unit tests. The chart maps an empty `storageClass` to `replicated` at one replica, and the PR lane runs LINSTOR without DRBD and creates only `local`, so the E2E fixture takes its class from the `storageClass` value the harness passes with `--set-string` from `COZY_E2E_STORAGE_CLASS`, the way the vminstance fixtures do; on the nightly QEMU lane that still resolves to `replicated`. And the external Dashboards Service selected labels no pod carries. `pkg/builders/dashboards.go` at v2.8.0 stamps `opensearch.cluster.dashboards: <cluster name>` on the Deployment, its selector and the pod template, and nothing else; the chart asked for `opster.io/opensearch-cluster` together with `app.kubernetes.io/component: dashboards`, so the LoadBalancer came up with no endpoints and no error to show for it. It selects the label the operator sets now. ### securityadmin cross-trust, still blocked on the DNS base Chart-managed HTTP TLS previously broke the operator's securityadmin reconciliation: the admin certificate was signed by the transport CA while the HTTP listener trusted the cert-manager CA, so the two never verified against each other and users and roles silently never applied. This chart puts one CA under both sides, handing the HTTP CA to the operator through `spec.security.tls.http.caSecret` so that it signs the admin certificate with the CA the listener trusts. That closes the CA mismatch. The other half, the job resolving a name the operator built from `cluster.local` on a cluster that does not use it, was closed separately and is on main, so the security configuration applies once this lands. No operator bump is required; the API exists in the pinned version. That path is version-gated upstream at OpenSearch 2.0.0: below it the operator falls back to the transport CA and the mismatch returns with no error anywhere. The chart therefore refuses chart-managed HTTP TLS on `version: v1` with an explicit render-time failure that names the mechanism and offers the alternatives, rather than letting it fail silently at runtime. ### Trust anchor for tenants The HTTP server's private key is not exposed to tenants. The chart renders a `TenantProjection` sentinel that names `<release>.http-ca` as its source; the CA-extraction controller publishes a `ca.crt`-only copy as `<release>.tenant-ca`, and the ResourceDefinition selects it with the engine-agnostic `internal.cozystack.io/tenant-ca` label. The sentinel is gated on the same condition as the chain, so a plaintext release renders no sentinel instead of one stuck at `SourceNotFound`. Tenants get what they need to verify the server and nothing more. ## Known limitations These are stated rather than left to be discovered: 1. **securityadmin needed both trust and reachability, and both are closed now.** This branch put one CA under the admin certificate and the HTTP listener. The other half was the operator resolving `<svc>.<ns>.svc.<DNS_BASE>` with `DNS_BASE` left at the vendored `cluster.local`, so the job waited on a name that never resolved whichever CA had signed; the platform now renders that value from `networking.clusterDomain` and it is on main, which is what unblocks this branch. 2. **The e2e suite reaches the move, not the chart bump that triggers it.** The suite above arrives at the chart-managed chain by removing `tls.issuer` from a running release, which leaves exactly the values an upgraded release arrives with. The one step it cannot run is the one where the previous chart version wrote the CR, because there is no second chart version to install from in this tree. Everything downstream of that write is exercised on a cluster. 3. **A reissue does not reach a running pod.** Neither service reloads its certificate, and cert-manager reissues on any change to `external`, the tenant host or the cluster domain, so an ordinary edit leaves the pods serving material that no longer matches their own names with no error, event or condition to show for it. Completing such a change is manual. So is removing the CA private key cert-manager leaves behind when TLS is turned off again, since the platform runs with `enableCertificateOwnerRef: false` and deleting a `Certificate` does not delete its `Secret`. `packages/apps/opensearch/README.md` carries both, with the commands. ### Downstream repositories `packages/apps/opensearch/values.schema.json` gains the `tls` object, so `cozystack/terraform-provider-cozystack` needs the field modelled for `cozystack_opensearch`; tracked in cozystack/terraform-provider-cozystack#41. ### Upgrade impact An existing `external: true` release with `tls.issuer` unset serves operator-issued HTTP TLS today and moves to chart-managed TLS on its first reconcile after this lands: the cluster rolls once and is re-anchored on a new per-release CA, so any client pinned to the operator's CA has to be repointed at the key-free `<release>.tenant-ca`. Setting `tls.issuer: operator` before the upgrade keeps that half as it is. Releases that are not external are untouched. Every existing release rolls once regardless of `tls.issuer` and `external`, because the pod template loses the operator's `init-sysctl` container; on a single-replica release that roll is the first one the operator can complete, since draining the only data node used to block every rolling restart. The published external-dns name changes on the same upgrade whatever `tls.issuer` says, because the Services are gated on `external` alone: they move from `<release>.<namespace>.<cluster-domain>`, an in-cluster name that never resolved outside the cluster, to `<release>.<tenant-host>` and `<release>-dashboards.<tenant-host>`. external-dns is configured upsert-only here, so the old record is not withdrawn and keeps pointing at the LoadBalancer until it is removed from the zone by hand. That cleanup is per zone rather than per release and nothing enumerates the records, so the README shows how to derive the list from the cluster. ### Release note ```release-note feat(opensearch)!: the OpenSearch HTTP API and Dashboards already served TLS, from the operator's own private CA and with a SAN built from cluster.local while the credentials Secret advertised the release on the platform domain; both certificates now come from a per-release cert-manager CA whose anchor the platform publishes into the tenant as <release>.tenant-ca. Any client that worked against the old endpoint was skipping verification, because no hostname it was handed could have matched that SAN. Existing external releases move from the operator's CA to the chart's on their first reconcile, and their published external-dns name moves from the in-cluster domain to <release>.<tenant-host> with the old record left in place; set tls.issuer: operator beforehand to opt out of the CA move. With dashboards.enabled the application name is limited to 41 characters, and to 32 when external is on as well; past either bound the chart fails the render and withholds every object in the release. A release already above a bound is not broken by the guard, it is told why it has not been upgrading: the Dashboards Service the operator builds from that name exceeds the 63-character limit for a DNS label, the operator returns that failure on every pass, and the reconcilers queued behind Dashboards, which are upgrade and restart and snapshot repository, have not run since the release was created. Set dashboards.enabled to false to drop the bound. The external Dashboards Service also selected labels the operator does not put on Dashboards pods, so it stood up with no endpoints; it selects opensearch.cluster.dashboards now. The drain of data nodes is now requested only with the data role on and more than two replicas, since at two the operator gives up on a full drain itself. The chart stops asking the operator for its privileged init-sysctl container, since the opensearch-operator package now sets vm.max_map_count from a DaemonSet, so every existing release rolls once on upgrade; single-replica releases no longer ask the operator to drain their only data node, which used to block every rolling restart ```
2 parents 080c649 + 76c9ece commit cecb4b1

29 files changed

Lines changed: 3420 additions & 32 deletions

‎api/apps/v1alpha1/opensearch/types.go‎

Lines changed: 12 additions & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎api/apps/v1alpha1/opensearch/zz_generated.deepcopy.go‎

Lines changed: 16 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 141 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,141 @@
1+
#!/usr/bin/env bats
2+
# Unit test: the opensearch ResourceDefinition hands tenants the key-free trust
3+
# anchor and nothing else.
4+
#
5+
# The chart issues opensearch-<name>.http-ca (CA certificate AND CA private key,
6+
# the latter under tls.key), opensearch-<name>-http-server and
7+
# opensearch-<name>-dashboards-server (each a server certificate AND its private
8+
# key). None may reach a tenant: read access to the CA key would let the holder
9+
# issue certificates for anything rather than merely verify the server. What a
10+
# client needs is ca.crt alone, delivered by the CA-extraction controller as the
11+
# key-free <release>.tenant-ca projection and selected by LABEL rather than by
12+
# name, because a name grant conveys whatever happens to occupy that name.
13+
#
14+
# Asserted against the RENDERED chart, not against cozyrds/opensearch.yaml on
15+
# disk. templates/cozyrd.yaml globs cozyrds/* and emits each match through
16+
# .Files.Get, so what ships is the render: reading one source file would miss a
17+
# second file in that directory, and a dotfile the glob picks up. Helm ignores
18+
# dotfiles only under templates/, so one here does ship. That is the whole reason
19+
# this file exists alongside hack/check-opensearch-readme.bats, which asserts the
20+
# same include shape by reading the one source file — narrower on purpose, and
21+
# blind to exactly this.
22+
#
23+
# This lives in bats rather than helm-unittest because packages/system/
24+
# opensearch-rd has no `test:` target, and hack/helm-unit-tests.sh skips any
25+
# package without one. If that package ever grows one, this belongs there.
26+
#
27+
# spec.secrets is compared WHOLE rather than probed for known-bad names. Three
28+
# ways this breaks are invisible to a name-by-name check:
29+
#
30+
# - a name added under a different spelling, or via a helper;
31+
# - an include with NO resourceNames and NO matchLabels, which restricts
32+
# nothing;
33+
# - a SECOND matchLabels include selecting a label the key-bearing Secrets also
34+
# carry. cert-manager stamps controller.cert-manager.io/fao on every Secret it
35+
# creates, all three of these among them, so one such entry grants the CA
36+
# private key while every name in the file stays correct.
37+
38+
REPO_ROOT="$(cd "$(dirname "${BATS_TEST_FILENAME:-$0}")/.." && pwd)"
39+
CHART="$REPO_ROOT/packages/system/opensearch-rd"
40+
41+
# The complete tenant-visible Secret surface. The credentials Secret by name; the
42+
# trust anchor by label. Nothing else.
43+
EXPECTED_SECRETS='{"exclude":[],"include":[{"resourceNames":["opensearch-{{ .name }}-credentials"]},{"matchLabels":{"internal.cozystack.io/tenant-ca":"true"}}]}'
44+
45+
# Order within include is meaningless -- the matcher ORs across entries -- so the
46+
# array is sorted before comparing, and a missing exclude is normalized to the
47+
# empty list it means. Neither can hide a grant: sort preserves every entry (it is
48+
# not unique), and exclude only ever narrows.
49+
#
50+
# Kept as a filter string rather than a shell function because hack/cozytest.sh
51+
# inserts `return 0` before any line that is exactly `}`. A helper whose own last
52+
# command decides the outcome returns 0 regardless -- and whether a wrapper
53+
# propagates a failure at all then depends on the shell running it. Repeating the
54+
# helm invocation inline in each test costs two lines and owes nothing to that.
55+
NORMALIZE='{exclude: (.exclude // []), include: (.include | sort)}'
56+
57+
# Every document count below uses `yq eval-all`, never `yq eval`. `eval` runs the
58+
# expression once PER DOCUMENT, so `[.] | length` reports 1 per document rather
59+
# than the number of documents. `eval-all` folds the stream into one expression.
60+
# Empty input still yields 1, since yq synthesizes a null document, so emptiness
61+
# is checked separately before counting.
62+
63+
@test "opensearch-rd renders exactly one ApplicationDefinition" {
64+
# stderr is deliberately not discarded: when the render breaks, helm's own
65+
# message is the only thing that says why.
66+
rendered=$(helm template opensearch-rd "$CHART") || return 1
67+
68+
# Fail closed: an empty render makes every assertion below vacuous, and yq
69+
# cannot distinguish it from one document.
70+
if [ -z "$rendered" ]; then
71+
echo "helm template produced no output for $CHART -- guard is blind." >&2
72+
return 1
73+
fi
74+
75+
count=$(printf '%s\n' "$rendered" | yq eval-all '[.] | length' -) || return 1
76+
77+
if [ "$count" != "1" ]; then
78+
echo "Expected exactly 1 rendered document from $CHART, got: $count" >&2
79+
echo "templates/cozyrd.yaml globs cozyrds/*, so every file there -- including" >&2
80+
echo "a dotfile -- ships its own tenant grants. Extend this suite before" >&2
81+
echo "adding one." >&2
82+
return 1
83+
fi
84+
}
85+
86+
@test "opensearch-rd selects the key-free tenant-CA projection by label" {
87+
rendered=$(helm template opensearch-rd "$CHART") || return 1
88+
89+
if [ -z "$rendered" ]; then
90+
echo "helm template produced no output for $CHART -- guard is blind." >&2
91+
return 1
92+
fi
93+
94+
count=$(printf '%s\n' "$rendered" | yq eval-all \
95+
'[.. | select(has("secrets")) | .secrets.include[] | select(.matchLabels."internal.cozystack.io/tenant-ca" == "true")] | length' \
96+
-) || return 1
97+
98+
if [ "$count" -lt 1 ]; then
99+
echo 'opensearch-rd does not select internal.cozystack.io/tenant-ca: "true"' >&2
100+
echo "Without it the tenant cannot read ca.crt and TLS verification is impossible." >&2
101+
return 1
102+
fi
103+
}
104+
105+
# Whole-structure comparison. Anything added to the tenant's Secret surface -- by
106+
# name, by label, or by an unrestricted entry -- changes this string.
107+
@test "opensearch-rd exposes no Secret beyond the credentials and the trust anchor" {
108+
rendered=$(helm template opensearch-rd "$CHART") || return 1
109+
110+
if [ -z "$rendered" ]; then
111+
echo "helm template produced no output for $CHART -- guard is blind." >&2
112+
return 1
113+
fi
114+
115+
# eval-all again: with `eval`, a second rendered document would emit a second
116+
# JSON object and the comparison below would run on a concatenation.
117+
actual=$(printf '%s\n' "$rendered" \
118+
| yq eval-all --output-format=json '[.. | select(has("secrets")) | .secrets]' - \
119+
| jq --sort-keys --compact-output "if length == 1 then .[0] else . end | $NORMALIZE") || return 1
120+
121+
expected=$(printf '%s' "$EXPECTED_SECRETS" \
122+
| jq --sort-keys --compact-output "$NORMALIZE") || return 1
123+
124+
# Fail closed: an empty or null result means spec.secrets stopped being readable
125+
# at this path, so the guard is no longer observing what it claims.
126+
if [ -z "$actual" ] || [ "$actual" = "null" ]; then
127+
echo "spec.secrets is missing or unreadable in the rendered ResourceDefinition -- guard is blind." >&2
128+
return 1
129+
fi
130+
131+
if [ "$actual" != "$expected" ]; then
132+
echo "Unexpected tenant Secret surface in the rendered opensearch-rd spec.secrets:" >&2
133+
echo " actual: $actual" >&2
134+
echo " expected: $expected" >&2
135+
echo "opensearch-<name>.http-ca holds the CA PRIVATE KEY, and -http-server and" >&2
136+
echo "-dashboards-server each hold a server private key. None may be granted to" >&2
137+
echo "a tenant, by name or by a label they also carry -- cert-manager stamps its" >&2
138+
echo "own labels on all three." >&2
139+
return 1
140+
fi
141+
}

‎hack/check-opensearch-readme.bats‎

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
#!/usr/bin/env bats
2+
# Tests that the opensearch README.md has the correct structure after generation.
3+
#
4+
# These are static checks on the committed README.md — they do not invoke
5+
# make generate (which requires cozyvalues-gen in PATH). They verify that:
6+
# 1. tls.issuer description is not truncated (ends with "on and off")
7+
# 2. topologySpreadPolicy appears outside the TLS section
8+
# 3. opensearch-rd cozyrds labels the tenant CA and no server certificate
9+
10+
REPO_ROOT="$(cd "$(dirname "${BATS_TEST_FILENAME:-$0}")/.." && pwd)"
11+
README="$REPO_ROOT/packages/apps/opensearch/README.md"
12+
COZYRDS="$REPO_ROOT/packages/system/opensearch-rd/cozyrds/opensearch.yaml"
13+
14+
@test "tls.issuer description is not truncated" {
15+
# The last clause of the @field line in values.yaml. cozyvalues-gen copies only
16+
# the first line of a description into the table, so a wrapped @field silently
17+
# loses its tail and the row still renders.
18+
grep -q "does switch TLS on and off" "$README"
19+
}
20+
21+
@test "topologySpreadPolicy is not in TLS configuration section" {
22+
# TLS section should contain only tls/tls.issuer rows, not topology spread.
23+
# The awk pattern skips the heading line itself, then prints until the next
24+
# section heading so the range is non-vacuous.
25+
#
26+
# if/exit rather than a `!` prefix, for the reason spelled out on the
27+
# publish-ca-cert check below: under hack/cozytest.sh a negated pipeline cannot
28+
# fail the test at all.
29+
if awk '/### TLS configuration/{found=1; next} found && /^### /{exit} found' "$README" | grep -q "topologySpreadPolicy"; then
30+
echo "topologySpreadPolicy appears inside the TLS configuration section" >&2
31+
exit 1
32+
fi
33+
}
34+
35+
@test "topologySpreadPolicy appears in README at all" {
36+
# Deliberately only presence. This is what stops the test above passing
37+
# vacuously: a README that lost the row entirely would satisfy "not in the TLS
38+
# section" without documenting the parameter anywhere. The "outside the TLS
39+
# section" half is that test's job, not this one's.
40+
grep -q "topologySpreadPolicy" "$README"
41+
}
42+
43+
@test "cozyrds opensearch.yaml labels the tenant CA for the tenant registry" {
44+
# The key-free trust anchor the CA-extraction controller publishes, selected by
45+
# label rather than by name. This entry is the whole tenant read path: it drives the
46+
# lineage webhook's tenantresource verdict, and the tenant reads the projection
47+
# through core.cozystack.io/tenantsecrets, which the base tenant roles grant. The
48+
# chart Role grants no name for it — tests/dashboard-resourcemap_test.yaml pins that.
49+
grep -q "internal.cozystack.io/tenant-ca" "$COZYRDS"
50+
}
51+
52+
@test "cozyrds opensearch.yaml exposes no server certificate to the tenant" {
53+
# A tenant needs ca.crt to verify the endpoint and nothing more. Both the leaf
54+
# Secret and the cert-manager CA Secret carry a private key under tls.key, so
55+
# neither may be listed here — only the controller's key-free projection.
56+
#
57+
# Asserted on the SHAPE of secrets.include, not by grepping one spelling: this is
58+
# the only thing standing between the CA private key and the tenant, and a name
59+
# written a different way, or a selector that happens to match a key-bearing
60+
# Secret, has to fail this too. Every entry must be one of exactly two known-safe
61+
# forms — the credentials Secret by name, or the tenant-ca projection by label.
62+
command -v yq >/dev/null || { echo "yq (mikefarah v4+) is required" >&2; exit 1; }
63+
64+
credentials='{"resourceNames":["opensearch-{{ .name }}-credentials"]}'
65+
tenant_ca='{"matchLabels":{"internal.cozystack.io/tenant-ca":"true"}}'
66+
67+
entries="$(yq --output-format=json -I=0 '.spec.secrets.include[]' "$COZYRDS")"
68+
69+
# Guard against a vacuous pass. A loop over nothing is a green test, and this one
70+
# guards tenant read access to a Secret holding the HTTP CA private key — so assert
71+
# the list is the size we think it is before concluding anything about its members.
72+
# Without this the test would still report ok if the path were restructured away.
73+
# `|| true` because grep exits non-zero on no match, which under set -e would kill
74+
# the test before the diagnostic below could explain what was expected.
75+
count="$(printf '%s\n' "$entries" | grep -c '^{' || true)"
76+
if [ "$count" -ne 2 ]; then
77+
echo "expected exactly 2 secrets.include entries, found $count" >&2
78+
printf '%s\n' "$entries" >&2
79+
return 1
80+
fi
81+
82+
while IFS= read -r entry; do
83+
[ -n "$entry" ] || continue
84+
if [ "$entry" != "$credentials" ] && [ "$entry" != "$tenant_ca" ]; then
85+
echo "secrets.include has an entry that is neither the credentials Secret" >&2
86+
echo "nor the key-free tenant-ca projection: $entry" >&2
87+
return 1
88+
fi
89+
done <<EOF
90+
$entries
91+
EOF
92+
}
93+
94+
@test "cozyrds opensearch.yaml selects the projection, never a publish source" {
95+
# publish-ca-cert was a label-driven extraction leg that never shipped: no
96+
# controller on main reads it. What ships is the TenantProjection sentinel, which
97+
# names its source Secret outright, and the only label in the mechanism is
98+
# tenant-ca on the projection the controller writes — which is what the selector
99+
# above matches.
100+
#
101+
# The assertion outlives the leg it was written for. A publish-ca-cert selector
102+
# here would be inert rather than dangerous today, but the name marked a
103+
# key-bearing SOURCE — the cert-manager CA Secret, private key under tls.key — so
104+
# reviving it as a selector is the one edit that would hand the tenant that key.
105+
# Cheaper to keep the name out of this file than to re-derive that each time.
106+
#
107+
# NOT written as `! grep -q`. These files run under hack/cozytest.sh, which
108+
# injects `return 0` ahead of the closing brace, and a `!`-prefixed pipeline is
109+
# exempt from set -e — so a bare negation reports green under the runner CI uses
110+
# while real bats fails it. if/exit is the form that survives both.
111+
if grep -q "internal.cozystack.io/publish-ca-cert" "$COZYRDS"; then
112+
echo "cozyrds selects on publish-ca-cert, which marks the key-bearing CA Secret" >&2
113+
exit 1
114+
fi
115+
}

‎hack/e2e-chainsaw/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ hack/e2e-chainsaw/
1818
└── ...
1919
```
2020

21-
Suites: `postgres`, `bucket`, `mariadb`, `mongodb`, `redis`, `qdrant`, `clickhouse`, `kafka`, `etcd`, `openbao`, `harbor`, `foundationdb`, `external-dns`, `kuberture`, `vminstance`, `gateway`, `kubernetes-latest`, `kubernetes-previous`, `securitygroup`.
21+
Suites: `postgres`, `bucket`, `mariadb`, `mongodb`, `redis`, `valkey`, `qdrant`, `clickhouse`, `kafka`, `rabbitmq`, `etcd`, `openbao`, `harbor`, `foundationdb`, `external-dns`, `kuberture`, `vminstance`, `gateway`, `opensearch`, `kubernetes-latest`, `kubernetes-previous`, `securitygroup`.
2222

2323
## What Chainsaw buys over the BATS suite
2424

0 commit comments

Comments
 (0)