Connection profiles for seven engines

A connection profile is a saved, named target: one MySQL server, one Redis instance, one Kafka bootstrap broker, or one kubeconfig context. DevOpsPad supports seven engine types, and every profile has a name, an environment label, the address or kubeconfig, credentials, optional TLS and an optional SSH tunnel.

Profiles are stored on your machine. The password and any SSH secrets go to the OS keychain; the rest is written to a local workspace file. Every profile is read-only in the query workbench, whatever the account’s server-side permissions.

Fields by engine

Field	MySQL	ClickHouse	MongoDB	Redis	Kafka	Kubernetes / K3s
Host and port	3306	8123 or 8443	27017	6379	9092	from kubeconfig
Username / password	yes	yes	yes	ACL user optional	SASL/PLAIN optional	from kubeconfig
Database	default database	default database	required	database number	—	namespace
Extra	—	HTTP interface	Authentication database	—	—	Kubeconfig file, Context
TLS	yes	yes (HTTPS)	yes	yes	yes	from kubeconfig
SSH tunnel	yes	yes	yes	yes	yes	yes

Engine-specific guides: MySQL, ClickHouse, MongoDB, Redis, Kafka, Kubernetes and K3s.

Kubernetes and K3s profiles

Both use the same client-go adapter and the same fields: a kubeconfig file, a context (or Current context) and a namespace. * or an empty namespace lists across all namespaces. Token and client-certificate authentication are supported; exec-based authentication plugins are rejected. Choosing K3s rather than Kubernetes only changes the label and icon. Cluster connections are listed under Infra → 集群资源 (cluster resources); database, cache and Kafka connections are listed in the 中间件 workbench.

See what an engine can do

Every connection card on the Connections page and the query toolbar have a capability link (the ? icon). It opens capabilities: the query language, the resource type, the features available in this release and Current limitations. For example, MySQL lists Read-only SQL, Table columns & indexes, DDL inspection and Database navigation, with the limitation that data editing and schema changes are not available yet.

The Your connections page with cards for MySQL, Redis, MongoDB, Kafka and ClickHouse connections, each showing its environment, host and capabilities

Connection status

DevOpsPad does not run background health checks. The header of an open connection shows the result of the last real request: Last response at a time, Last request failed, or Not yet verified. A cached resource list is not treated as proof that the connection is up. Use Test connection for an explicit check.

Limits

One host per profile. MongoDB SRV and replica-set profiles, Redis Cluster and Sentinel, and multi-broker Kafka bootstrap lists are not supported yet.
Custom CA files and client certificates for databases are not supported; see TLS options.
Profiles are personal to the machine. There is no sync or team sharing of connections.