Open philip-teleport opened 1 year ago
The Helm chart specifications implie that it is possible https://goteleport.com/docs/reference/helm-reference/teleport-kube-agent/#azuredatabases However, it does not explain how to use a Managed Identity rather than an App Registration when the latter isn't recommended for production environment
Registering the Database Service as Azure AD application is suitable for test and development scenarios, or if your Database Service does not run on an Azure VM. For production scenarios prefer to use the managed identity approach.
Applies To
Database Access with SQL Server on Azure
Details
The guide and integration focuses on using an Azure Compute VM to host the Teleport Database Service and requires that two managed identities (System-assigned and User-assigned) are assigned to the Azure Compute VM; see here.
The
teleport-kube-agent
running on Azure Kubernetes Service (AKS) can also host thedatabase_service
but it is unclear if this option is supported for Azure SQL Server as AKS services do not use “virtual machines” instead they use “virtual machine Scale-Sets” and attempts to assign the managed identities to the Azure AKS scale-set have been unsuccessful.How will we know this is resolved?
Documentation is updated to either:
database_service
hosted by theteleport-kube-agent
running on Azure Kubernetes Service (AKS); ORdatabase_service
.Related Issues
N/A