Skip to content

Commit 497768a

Browse files
committed
Update to clarify endpoints.
1 parent c39728d commit 497768a

1 file changed

Lines changed: 8 additions & 5 deletions

File tree

docs/linux/sql-server-linux-kubernetes-deploy.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ On Kubernetes the deployment includes a SQL Server operator, the SQL Server cont
8181
Copy the SQL Server manifest [`sqlserver.yaml`](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/high%20availability/Kubernetes/sample-manifest-files/sqlserver.yaml) from [sql-server-samples](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/high%20availability/Kubernetes/sample-manifest-files).
8282

8383
>[!NOTE]
84-
>The `sqlserver.yaml` file describes the SQL Server containers, persistent volume claims, and persistent volumes that are required for the storage for each SQL Server instance.
84+
>The `sqlserver.yaml` file describes the SQL Server containers, persistent volume claims, persistent volumes, and load-balancing services that are required for each SQL Server instance.
8585
8686
Apply the manifest to the Kubernetes cluster.
8787

@@ -101,8 +101,8 @@ Use `az aks browse` to launch the dashboard.
101101

102102
The [`ag-services.yaml`](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/high%20availability/Kubernetes/sample-manifest-files/ag-services.yaml) from [sql-server-samples](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/high%20availability/Kubernetes/sample-manifest-files) example describes load-balancing services that can connect to availability group replicas.
103103

104-
- `ag1-primary` connects to the primary replica.
105-
- `ag1-secondary` connects to any secondary replica.
104+
- `ag1-primary` provides an endpoint to connect to the primary replica of the AG.
105+
- `ag1-secondary` provides an endpoint to connect to any secondary replica.
106106

107107
When you apply the manifest file in the example, Kubernetes creates the load-balancing services for each type of replica. The load-balancing service includes an IP address. Use this IP address to connect to the type of replica you need.
108108

@@ -120,8 +120,11 @@ With the IP address, you can connect to the SQL Server instance that hosts each
120120

121121
The following image shows:
122122

123-
1. The output from `kubectl get services` for the namespace `ag1`.
124-
1. The connection to the replica, with `sqlcmd`, and the `sa` account.
123+
- The output from `kubectl get services` for the namespace `ag1`.
124+
125+
This includes the load-balancing services that are created for each SQL Server container. You can use these IP addresses as endpoints to connect directly to the instances of SQL Server in the cluster.
126+
127+
- The `sqlcmd` connection to the primary replica, with the `sa` account via the load-balancer endpoint.
125128

126129
![connect](./media/sql-server-linux-kubernetes-deploy/connect.png)
127130

0 commit comments

Comments
 (0)