Kvindo™ Cloud Docs
A managed Valkey cluster with a reusable Parameter Set for cache-tuned eviction settings, and a Valkey User — an ACL user scoped to read/write access on one key prefix and one pub/sub channel, rather than the cluster's own admin credentials. Assumes the Networking example's demo network is already applied. kc resolves a name reference like parametersSetId because it sits directly on spec, but not the shard's vpcSubnetId below (it's nested inside a list) — so the subnet's real ID is looked up and captured into a shell variable first, making the whole block directly runnable.
Once reconciled, read the connection URI a client would actually use: kc get valkey main -n demo -o json | jq -r .status.connectionUri.
Resource docs
More in this section