DevOpsPadDownload

Add your first connection

Choose New connection (or press ⌘ N / Ctrl N), pick an engine, fill in the address and credentials, click Test connection, and then Save connection. The connection appears in the Explorer on the left (cluster connections appear under Infra); select it to browse its databases, tables, keys, topics or cluster resources.

A connection never runs anything you did not ask for. Saving stores the metadata locally and the password in the OS keychain, and browsing only reads.

1. Open the dialog

Use any of these:

  • The + button in the navigation rail or next to CONNECTIONS in the Explorer.
  • New connection on an empty workspace.
  • ⌘ N on macOS or Ctrl N elsewhere.

2. Pick an engine

The top of the dialog lists MySQL, Redis, MongoDB, Kafka, ClickHouse, Kubernetes and K3s. Picking one sets its default port:

Engine Default port
MySQL 3306
Redis 6379
MongoDB 27017
Kafka 9092
ClickHouse 8123 (HTTP interface)
Kubernetes / K3s from your kubeconfig

The New connection dialog with MySQL selected: connection name, environment, host, port, username, password, database, TLS and SSH tunnel options

3. Fill in the details

For databases, caches and Kafka:

  1. Connection name, for example Orders replica. Required.
  2. Environment: Development, Staging, Production, or your own label. See environment labels.
  3. Host and Port. Enter a hostname or IP address without a scheme such as https://.
  4. Username and Password. For a least-privilege account, see least-privilege accounts.
  5. Database: the default database for MySQL and ClickHouse, the database number for Redis (default 0), and the database name for MongoDB (required). Kafka has no database field.
  6. Use TLS with certificate verification if the server requires TLS. See TLS options.

For Kubernetes and K3s, choose a Kubeconfig file, then a Context and a Namespace (* lists all namespaces). See kubeconfig contexts.

If the target is only reachable through a bastion host, turn on Connect through SSH tunnel. See the SSH tunnel overview.

4. Test, then save

Click Test connection. DevOpsPad performs the engine’s real check (for example a MySQL ping or a Redis PING) and reports Connection verified in N ms, or the exact error. Then click Save connection.

5. Browse and query

Select the connection in the Explorer. DevOpsPad loads its resources: databases and tables, Redis keys, MongoDB collections or Kafka topics. Kubernetes and K3s connections are listed under Infra → 集群资源 (cluster resources) instead of the 中间件 Explorer. Open a table, key or collection to get a query tab, edit the query and press ⌘ Enter to run it. Next: query tabs.

Common errors

  • Enter a hostname or IP address without a URL scheme: remove http://, paths or user@ from the host.
  • Redis database must be a non-negative integer: Redis databases are numbers such as 0 or 3.
  • Kubeconfig path is required: Kubernetes and K3s connections need a kubeconfig file.
  • Buttons are disabled: you are in the browser preview. Connections can only be tested and saved in the desktop app.