My updated course “Configuring and Managing Kubernetes Networking, Services, and Ingress” is now available on Pluralsight here! If you want to learn about the course, check out the trailer here, or if you’re going to dive right in, check it out here!
It’s time to dig deeper into Kubernetes networking! You will learn Kubernetes cluster networking fundamentals and configuring and accessing applications in a Kubernetes Cluster with Services and Ingress.
This post will walk you through setting file permissions on database files copied into a container. The SQL Server process sqlservr running in containers runs as the non-privileged user mssql. The appropriate permissions on files are needed, so the SQL Server process has the proper access to any database files, log files, and backup files.
Start up a container First up, let’s start up a container. Here’s we’re starting up SQL Server 2019 CU11 and attaching a Docker data volume for our persistent data.
My updated course “Managing Kubernetes Controllers and Deployments” is now available on Pluralsight here! If you want to learn about the course, check out the trailer here or if you want to dive right in check it out here! Learn how to deploy and maintain applications using Kubernetes Controllers. In this course you’ll learn how to select a Controller for your workload, deploy it, and maintain your container-based applications in your Kubernetes cluster.
In this blog post, we will walk through a few examples of configuring SQL Server in Kubernetes. First, we will create a Deployment for SQL Server, override the container’s command, and specify a Database Engine Service Startup Option. Second, we will create a Deployment for SQL Server using a ConfigMap to inject an mssql.conf configuration file.
Creating a SQL Server Deployment and Overriding the Container’s Command and Arguments First up, let’s create a Deployment for SQL Server and override the container’s command specify a Database Engine Service Startup Option.
In this blog post, we will walk through a few examples of how to configure SQL Server in Docker Containers. First, we will configure a container at runtime by overriding the default docker command for the container and setting Database Engine Service Startup Options. Second, we’re going to inject a configuration file into our container to configure SQL Server. Let’s go!
Starting a Container with a Trace Flag First up, let’s configure a container at runtime using Database Engine Service Startup Options.
Limits in Containers Docker gives you the ability to control a container’s access to CPU, Memory, and network and disk IO using resource constraints, sometimes called Limits. You define limits as parameters when creating containers. In its default configuration, a container will have no resource constraints for accessing resources of the host operating system. This post will look at how to configure resource constraints in Docker and look at how SQL Server sees the resources when CPU and Memory resource constraints are in place.
I want to start by saying thank you to all who submitted, and an amazing collection of people submitted some fantastic content. Also, thanks to Steve for asking me to host and being patient with me for mixing up the dates and the hashtag. It’s #tsql2sday and it’s on Tuesday not Wednesday :P
Now, onto the posts in submission order.
Rob Farley – On containers
Rob discusses how he uses containers to quickly spin up SQL Server instances without installing them on his local OS, replacing the virtual machine-based environments he used in the past.
My updated course “Managing the Kubernetes API Server and Pods” is now available on Pluralsight here! If you want to learn about the course, check out the trailer here or if you want to dive right in check it out here! This course targets IT professionals that design and maintain Kubernetes and container based solutions. The course can be used by both the IT pro learning new skills and the system administrator or developer preparing for using Kubernetes both on premises and in the Cloud.
My updated course “Kubernetes Installation and Configuration Fundamentals” is now available on Pluralsight here! If you want to learn about the course, check out the trailer here or if you want to dive right in check it out here! This course targets IT professionals that design and maintain Kubernetes and container based solutions. The course can be used by both the IT pro learning new skills and the system administrator or developer preparing for using Kubernetes both on premises and in the Cloud.
In this post, we will explore how a Pod name is generated, Pod Name lifecycle, how it’s used inside a Pod to set the system hostname, and how the system hostname is used by SQL Server to set its server name metadata.
Pod Naming in Deployments When deploying SQL Server in Kubernetes using a Deployment, the Pod created by the Deployment Controller will have a name with a structure of <DeploymentName>-<PodTemplateHash>-<PodID> for example, mssql-deployment-8cbdc8ddd-9n7jh.
