| copyright |
|
||
|---|---|---|---|
| lastupdated | 2024-12-05 | ||
| keywords | postgresql, databases, postgresql connection strings, postgresql connection ibm application | ||
| subcollection | databases-for-postgresql |
{:external: .external target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:codeblock: .codeblock} {:pre: .pre} {:tip: .tip} {:deprecated: .deprecated} {{site.data.keyword.attribute-definition-list}}
{: #ibmcloud-app}
Applications running in {{site.data.keyword.cloud_notm}} can be bound to your {{site.data.keyword.databases-for-postgresql_full}} deployment.
{: #connect-kubernetes}
There are two steps to connecting a Cloud databases deployment to a Kubernetes Service application. First, your deployment needs to be bound to your cluster and its connection strings that are stored in a secret. The second step is configuring your application to use the connection strings.
The sample app in the Connecting a Kubernetes Service Tutorial provides a sample application that uses Node.js and demonstrates how to bind the sample application to a {{site.data.keyword.databases-for}} deployment. {: .tip}
Before connecting your Kubernetes Service application to a deployment, make sure that the deployment and cluster are both in the same region and resource group.
{: #bind-deployment}
Public endpoints - If you are using the default public service endpoint to connect to your deployment, you can run the cluster service bind command with your cluster name, the resource group, and your deployment name.
ibmcloud ks cluster service bind <CLUSTER_NAME> <RESOURCE_GROUP> <DEPLOYMENT_NAME_OR_CRN>{: pre}
OR Private endpoints - If you want to use a private endpoint (if one is enabled on your deployment), then create a service key for Kubernetes to use when binding to the database.
ibmcloud resource service-key-create <PRIVATE_KEY> --instance-name <DEPLOYMENT_NAME_OR_CRN> --service-endpoint private {: pre}
The private service endpoint is selected with --service-endpoint private. After that, you bind the database to the Kubernetes cluster through the private endpoint with the cluster service bind command.
ibmcloud ks cluster service bind <CLUSTER_NAME> <RESOURCE_GROUP> <DEPLOYMENT_NAME_OR_CRN> --key <PRIVATE_KEY>{: pre}
Verify - Verify that the Kubernetes secret was created in your cluster namespace. Running the following command, you get the API key for accessing the instance of your deployment that is provisioned in your account.
kubectl get secrets --namespace=default{: pre}
More information on binding services is found in the Kubernetes Service documentation.
{: #configure-kubernetes}
When you bind your application to Kubernetes Service, it creates an environment variable from the cluster's secrets. Your deployment's connection information lives in BINDING as a JSON object. Load and parse the JSON object into your application to retrieve the information your application's driver needs to make a connection to the database.
The Connection strings page contains a reference of the JSON fields.
For more information, see the Kubernetes Service documentation.