119 lines
4.7 KiB
Markdown
119 lines
4.7 KiB
Markdown
---
|
|
title: "AzureDNS"
|
|
date: 2019-03-03T16:39:46+01:00
|
|
draft: false
|
|
slug: azuredns
|
|
dnsprovider:
|
|
since: "v0.1.0"
|
|
code: "azuredns"
|
|
url: "https://azure.microsoft.com/services/dns/"
|
|
---
|
|
|
|
<!-- THIS DOCUMENTATION IS AUTO-GENERATED. PLEASE DO NOT EDIT. -->
|
|
<!-- providers/dns/azuredns/azuredns.toml -->
|
|
<!-- THIS DOCUMENTATION IS AUTO-GENERATED. PLEASE DO NOT EDIT. -->
|
|
|
|
|
|
Configuration for [AzureDNS](https://azure.microsoft.com/services/dns/).
|
|
|
|
|
|
<!--more-->
|
|
|
|
- Code: `azuredns`
|
|
- Since: v0.1.0
|
|
|
|
|
|
Here is an example bash command using the AzureDNS provider:
|
|
|
|
```bash
|
|
### Using client secret
|
|
AZURE_CLIENT_ID=<your service principal client ID> \
|
|
AZURE_TENANT_ID=<your service principal tenant ID> \
|
|
AZURE_CLIENT_SECRET=<your service principal client secret> \
|
|
lego --domains example.com --email your_example@email.com --dns azuredns run
|
|
|
|
### Using client certificate
|
|
AZURE_CLIENT_ID=<your service principal client ID> \
|
|
AZURE_TENANT_ID=<your service principal tenant ID> \
|
|
AZURE_CLIENT_CERTIFICATE_PATH=<your service principal certificate path> \
|
|
lego --domains example.com --email your_example@email.com --dns azuredns run
|
|
|
|
### Using Azure CLI
|
|
az login \
|
|
lego --domains example.com --email your_example@email.com --dns azuredns run
|
|
```
|
|
|
|
|
|
|
|
|
|
## Credentials
|
|
|
|
| Environment Variable Name | Description |
|
|
|-----------------------|-------------|
|
|
| `AZURE_CLIENT_ID` | Client ID |
|
|
| `AZURE_CLIENT_SECRET` | Client secret |
|
|
| `AZURE_RESOURCE_GROUP` | DNS zone resource group |
|
|
| `AZURE_SUBSCRIPTION_ID` | DNS zone subscription ID |
|
|
| `AZURE_TENANT_ID` | Tenant ID |
|
|
|
|
The environment variable names can be suffixed by `_FILE` to reference a file instead of a value.
|
|
More information [here]({{< ref "dns#configuration-and-credentials" >}}).
|
|
|
|
|
|
## Additional Configuration
|
|
|
|
| Environment Variable Name | Description |
|
|
|--------------------------------|-------------|
|
|
| `AZURE_ENVIRONMENT` | Azure environment, one of: public, usgovernment, and china |
|
|
| `AZURE_POLLING_INTERVAL` | Time between DNS propagation check |
|
|
| `AZURE_PRIVATE_ZONE` | Set to true to use Azure Private DNS Zones and not public |
|
|
| `AZURE_PROPAGATION_TIMEOUT` | Maximum waiting time for DNS propagation |
|
|
| `AZURE_TTL` | The TTL of the TXT record used for the DNS challenge |
|
|
| `AZURE_ZONE_NAME` | Zone name to use inside Azure DNS service to add the TXT record in |
|
|
|
|
The environment variable names can be suffixed by `_FILE` to reference a file instead of a value.
|
|
More information [here]({{< ref "dns#configuration-and-credentials" >}}).
|
|
|
|
## Description
|
|
|
|
Azure Credentials are automatically detected in the following locations and prioritized in the following order:
|
|
|
|
1. Environment variables for client secret: `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_SECRET`
|
|
2. Environment variables for client certificate: `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_CERTIFICATE_PATH`
|
|
3. Workload identity for resources hosted in Azure environment (see below)
|
|
4. Shared credentials file (defaults to `~/.azure`), used by Azure CLI
|
|
|
|
Link:
|
|
- [Azure Authentication](https://learn.microsoft.com/en-us/azure/developer/go/azure-sdk-authentication)
|
|
|
|
### Workload identity
|
|
|
|
#### Azure Managed Identity
|
|
|
|
Azure managed identity service allows linking Azure AD identities to Azure resources. \
|
|
Workloads running inside compute typed resource can inherit from this configuration to get rights on Azure resources.
|
|
|
|
#### Workload identity for AKS
|
|
|
|
Workload identity allows workloads running Azure Kubernetes Services (AKS) clusters to authenticate as an Azure AD application identity using federated credentials. \
|
|
This must be configured in kubernetes workload deployment in one hand and on the Azure AD application registration in the other hand. \
|
|
|
|
Here is a summary of the steps to follow to use it :
|
|
* create a `ServiceAccount` resource, add following annotations to reference the targeted Azure AD application registration : `azure.workload.identity/client-id` and `azure.workload.identity/tenant-id`. \
|
|
* on the `Deployment` resource you must reference the previous `ServiceAccount` and add the following label : `azure.workload.identity/use: "true"`.
|
|
* create a fedreated credentials of type `Kubernetes accessing Azure resources`, add the cluster issuer URL and add the namespace and name of your kubernetes service account.
|
|
|
|
Link :
|
|
- [Azure AD Workload identity](https://azure.github.io/azure-workload-identity/docs/topics/service-account-labels-and-annotations.html)
|
|
|
|
|
|
|
|
|
|
## More information
|
|
|
|
- [API documentation](https://docs.microsoft.com/en-us/go/azure/)
|
|
- [Go client](https://github.com/Azure/azure-sdk-for-go)
|
|
|
|
<!-- THIS DOCUMENTATION IS AUTO-GENERATED. PLEASE DO NOT EDIT. -->
|
|
<!-- providers/dns/azuredns/azuredns.toml -->
|
|
<!-- THIS DOCUMENTATION IS AUTO-GENERATED. PLEASE DO NOT EDIT. -->
|