Data-service connections

Two connection paths

For Kubernetes targets, select a cluster, namespace and Service/Pod. Battani reaches it through an on-demand tunnel bound to the server’s loopback interface. Direct connections use a host and port reachable from the Battani server.

A connection record contains the target, service type, TLS preferences and access policy. RabbitMQ can define separate messaging and management endpoints.

Credentials and sharing

• Kubernetes Secret reference: fields are resolved server-side when connecting.
• Manual credentials: stored encrypted on the server; list responses do not contain the actual password.
• Configure TLS and the real server name where required.
• Personal or system scope, with read, write or admin grants for users/teams.
• A read-only connection setting blocks mutating operations.

Prepare a new connection

SQL read-only access requires a separate least-privilege database account. The free-edition quota is 1 connection per type and 3 active connections in total. Testing requires its own permission because it opens a real target connection.

1. Choose the service type and target mode under Data Services.
2. Fill in endpoints, authentication and TLS settings. Start with read-only access.
3. Run the connection test and check which stages succeeded or failed.
4. Open the record to enter its console, then share the appropriate access level with the people who need it.