Kvindo™ Cloud Docs
A PostgreSQL Role is a login role inside a specific PostgreSQL Cluster's own catalog. It is the real access path for that cluster — the cluster resource itself has no user-facing credential, so create at least one Role to actually connect.
• Belongs to one cluster forever — spec.postgreSqlId is required and immutable; a role cannot move between clusters
• Write-only password — spec.password is never echoed back by the API, same as every other credential field on this platform; a modify that omits it re-sends whatever was typed, so leave it populated when changing other fields
• No default role — creating a cluster does not create a role automatically; this mirrors how a fresh Kubernetes cluster has no default KubernetesUser either
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| PostgreSql cluster | spec.postgreSqlId |
spec.postgresql_id |
No | ULID — references a PostgreSql cluster | — | No | Immutable after creation |
| Password | spec.password |
spec.password |
Yes | string (sensitive, write-only) | — | No | Never returned in status |
| Login | spec.login |
spec.login |
No | boolean | — | No | A login role with no password can never actually connect |
| Connection limit | spec.connectionLimit |
spec.connection_limit |
Yes | integer | unlimited | No | Maximum concurrent connections for this role |
A login role on an existing cluster. Terraform and Python SDK support are planned for a later release.
kc CLI
Resource docs
More in this section