Estimated Duration: 60 minutes
You need to fulfill these requirements and AKS Basic Cluster to complete this exercise.
Storage options for applications in AKS Quickstart: Deploy a SQL Server container cluster on Azure Best practices for storage and backups in AKS
A persistent volume claim (PVC) requests storage of a particular storage class, access mode, and size. The Kubernetes API server can dynamically provision the underlying Azure Storage resource if no existing resource can fulfill the claim based on the defined storage class.
| Use case | Volume plugin | Read/write once | Read-only many | Read/write many | Windows Server container support |
|---|---|---|---|---|---|
| Shared configuration | Azure Files | Yes | Yes | Yes | Yes |
| Structured app data | Azure Disks | Yes | No | No | Yes |
| Unstructured data, file system operations | BlobFuse | Yes | Yes | Yes | No |
In a terminal, export variables required for this lab (if not already exported):
INITIALS=abc
CLUSTER_NAME=aks-$INITIALS
RG=aks-$INITIALS-rgIf not already connected, connect to the cluster from your local client machine.
az aks get-credentials --name $CLUSTER_NAME -g $RGBy default, the password must be at least eight characters long and contain characters from three of the following four sets: uppercase letters, lowercase letters, base-10 digits, and symbols.
SA_PASSWORD=<value>Create a secret in Kubernetes named mssql that holds the MSSQL_SA_PASSWORD value, run the following command
kubectl create namespace sql
kubectl -n sql create secret generic mssql --from-literal=MSSQL_SA_PASSWORD="$SA_PASSWORD"Review the manifests/sql-pvc.yaml. It defines the storage class and the persistent volume claim. The manifest specifies the storage provisioner, parameters, and reclaim policy. The Kubernetes cluster uses this manifest to create the persistent storage.
The storage class provisioner is azure-disk, because this Kubernetes cluster is in Azure. The storage account type is Standard_LRS. The persistent volume claim is named mssql-data. The persistent volume claim metadata includes an annotation connecting it back to the storage class.
kubectl -n sql apply -f manifests/sql-pvc.yamlThe persistent volume is automatically created as an Azure storage account, and bound to the persistent volume claim. Verify the persistent volume claim, the persistent volume and storage class have been created:
kubectl get sc,pvc,pv -n sqlReview the manifests/sql-deployment.yaml file. The manifest defines a deployment, including a container based on the SQL Server container image.
In the security context, we define the fsGroup with the value 10001, which is the Group ID (GID) for the mssql group. This value means that all processes of the container are also part of the supplementary GID 10001 (mssql). The owner for volume /var/opt/mssql and any files created in that volume will be GID 10001 (the mssql group).
NOTE: By using the
LoadBalancerservice type, the SQL Server instance is accessible remotely (via the Internet) at port 1433.
kubectl -n sql apply -f manifests/sql-deployment.yamlView the status of the deployment:
kubectl get deployment,service,pod -n sqlGet the SQL pod name:
POD_NAME=$(kubectl -n sql get pod -o custom-columns=:metadata.name | awk NF)Verify the pod is RUNNNING:
kubectl -n sql describe pod $POD_NAMEConnect to the pod:
kubectl exec $POD_NAME -n sql -it -- /bin/bashYou can see the username as mssql if you run whoami. mssql is a non-root user.
whoamiFrom Visual Studio Code click on the Extensions toolbar icon. Type SQL and you then click on "SQL Server (mssql) form the search results, then click on Install:
Get the SQL Server service IP:
kubectl get svc mssql-deployment -n sql -o jsonpath='{.status.loadBalancer.ingress[0].ip}'From Visual Studio Code click on the "SQL Server" extension toolbar icon, then click on Add Connection. When prompted enter the IP as the Server Name, enter master as the Database name. Click on SQL Login and provide the sa User name and password.
Delete the namespace from AKS:
kubectl delete namespace sql