azure.azcollection.azure_rm_loadbalancerbackendaddresspool module – Manage a backend address pool of an Azure load balancer
Note
This module is part of the azure.azcollection collection (version 4.2.0).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install azure.azcollection.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: azure.azcollection.azure_rm_loadbalancerbackendaddresspool.
New in azure.azcollection 4.0.0
Synopsis
Create, update or delete a single backend address pool on an existing Azure load balancer.
The parent module azure.azcollection.azure_rm_loadbalancer only declares empty pool stubs by name.
This module owns all pool-level properties and members.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.7
The host that executes this module must have the azure.azcollection collection installed via galaxy
All python packages listed in collection’s requirements.txt must be installed via pip on the host that executes modules from azure.azcollection
Full installation instructions may be found https://galaxy.ansible.com/azure/azcollection
Parameters
Parameter |
Comments |
|---|---|
Active Directory username. Use when authenticating with an Active Directory user rather than service principal. |
|
Azure AD authority url. Use when authenticating with Username/password, and has your own ADFS authority. |
|
Selects an API profile to use when communicating with Azure services. Default value of Default: |
|
Controls the source of the credentials to use for authentication. Can also be set via the When set to When set to When set to When set to When set to The Choices:
|
|
Controls the certificate validation behavior for Azure endpoints. By default, all modules will validate the server certificate, but when an HTTPS proxy is in use, or against Azure Stack, it may be necessary to disable this behavior by passing Choices:
|
|
Azure client ID. Use when authenticating with a Service Principal or Managed Identity (msi). Can also be set via the |
|
For cloud environments other than the US public cloud, the environment name (as defined by Azure Python SDK, eg, Default: |
|
Determines whether or not instance discovery is performed when attempting to authenticate. Setting this to true will completely disable both instance discovery and authority validation. This functionality is intended for use in scenarios where the metadata endpoint cannot be reached such as in private clouds or Azure Stack. The process of instance discovery entails retrieving authority metadata from https://login.microsoft.com/ to validate the authority. By setting this to **True**, the validation of the authority is disabled. As a result, it is crucial to ensure that the configured authority host is valid and trustworthy. Set via credential file profile or the Choices:
|
|
Seconds the load balancer waits before sending RESET to client and backend address on connection close. |
|
Backend addresses (IP-based or NIC-config-based) for the backend pool. Requires Standard SKU load balancer. |
|
Administrative state which can override health probe results for this backend address. Choices:
|
|
IP address belonging to the referenced virtual_network. |
|
Resource ID of a regional load balancer frontend IP configuration. Used only when attaching a regional load balancer to a Global cross-region load balancer. |
|
Name of the backend address, unique within the pool. |
|
Resource ID of an existing NIC IP configuration to attach to the pool. |
|
Resource ID of the subnet the backend address belongs to. |
|
Resource ID of the virtual network the backend address belongs to. |
|
Name of the parent load balancer. |
|
Parent argument. |
|
Parent argument. |
|
Name of the backend address pool. |
|
Direct OpenID Connect (OIDC) token (JWT) used for workload identity authentication. This token is exchanged with Azure AD using OIDC federated identity. Useful in CI systems (for example GitHub Actions, Azure DevOps) where an OIDC token is provided directly by the platform. Can also be set via the |
|
Path to a file containing an OpenID Connect (OIDC) token (JWT) used for workload identity authentication. The file must contain only raw token. This method is commonly used in platforms that materialize OIDC tokens as files Can also be set via the |
|
Active Directory user password. Use when authenticating with an Active Directory user rather than service principal. |
|
Security profile found in ~/.azure/credentials file. |
|
Name of the resource group that contains the load balancer. |
|
Azure client secret. Use when authenticating with a Service Principal. |
|
Assert the state of the backend address pool. Use Choices:
|
|
Your Azure subscription Id. |
|
Backend address synchronous mode for the backend pool. Requires Standard SKU load balancer and virtual_network to be set. Choices:
|
|
Azure tenant ID. Use when authenticating with a Service Principal. |
|
The thumbprint of the private key specified in x509_certificate_path. Use when authenticating with a Service Principal. Required if x509_certificate_path is defined. |
|
Gateway load balancer tunnel interfaces for the backend address pool. |
|
Identifier of the gateway load balancer tunnel interface. |
|
Port of the gateway load balancer tunnel interface. |
|
Protocol of the gateway load balancer tunnel interface. Choices:
|
|
Traffic type of the gateway load balancer tunnel interface. Choices:
|
|
Resource ID of the virtual network the backend address pool is bound to. Required when sync_mode is set. |
|
Path to the X509 certificate used to create the service principal in PEM format. The certificate must be appended to the private key. Use when authenticating with a Service Principal. |
Notes
Note
For authentication with Azure you can pass parameters, set environment variables, use a profile stored in ~/.azure/credentials, or log in before you run your tasks or playbook with
az login.Authentication is also possible using a service principal or Active Directory user.
To authenticate via OIDC, pass client_id, tenant and oidc_token or oidc_token_file_path, or set environment variables AZURE_CLIENT_ID, AZURE_TENANT and AZURE_FEDERATED_TOKEN or AZURE_FEDERATED_TOKEN_FILE.
To authenticate via service principal, pass subscription_id, client_id, secret and tenant or set environment variables AZURE_SUBSCRIPTION_ID, AZURE_CLIENT_ID, AZURE_SECRET and AZURE_TENANT.
To authenticate via Active Directory user, pass ad_user and password, or set AZURE_AD_USER and AZURE_PASSWORD in the environment.
Alternatively, credentials can be stored in ~/.azure/credentials. This is an ini file containing a [default] section and the following keys: subscription_id, client_id, secret and tenant or subscription_id, ad_user and password. It is also possible to add additional profiles. Specify the profile by passing profile or setting AZURE_PROFILE in the environment.
See Also
See also
- Sign in with Azure CLI
How to authenticate using the
az logincommand.
Examples
- name: Create backend address pool with two IP-based members
azure_rm_loadbalancerbackendaddresspool:
resource_group: myResourceGroup
load_balancer_name: myLoadBalancer
name: bepool0
load_balancer_backend_addresses:
- name: address1
ip_address: 10.0.0.10
virtual_network: /subscriptions/xxx/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVnet
- name: address2
ip_address: 10.0.0.11
virtual_network: /subscriptions/xxx/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVnet
- name: Attach an existing NIC IP configuration to a backend pool
azure_rm_loadbalancerbackendaddresspool:
resource_group: myResourceGroup
load_balancer_name: myLoadBalancer
name: bepool0
load_balancer_backend_addresses:
- name: web-server1-nic
network_interface_ip_configuration: >-
/subscriptions/xxx/resourceGroups/myResourceGroup/providers/Microsoft.Network/networkInterfaces/web1-nic/ipConfigurations/ipconfig1
- name: Delete backend address pool
azure_rm_loadbalancerbackendaddresspool:
resource_group: myResourceGroup
load_balancer_name: myLoadBalancer
name: bepool0
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
Whether or not the resource has changed. Returned: always |
|
Current state of the backend address pool. Returned: always |
|
Drain period in seconds. Returned: when-used |
|
Resource ID of the backend address pool. Returned: always Sample: |
|
List of backend addresses attached to the pool. Returned: always Sample: |
|
Name of the backend address pool. Returned: always Sample: |
|
Provisioning state of the backend address pool. Returned: always Sample: |
|
Backend address synchronous mode. Returned: when-used |
|
Gateway load balancer tunnel interfaces. Returned: when-used |
|
Resource ID of the virtual network the pool is bound to. Returned: when-used |