Sep 02, 2015 The following is an example of using BIG-IP to automate the routing of HTTP and DNS requests for containers across a Docker cluster. The process for connecting Docker to BIG-IP will involve exporting the list of containers that are running on a Docker host and enabling a process to route HTTP and DNS requests to the appropriate Docker container.
This topic applies to Docker Enterprise.
The Docker Enterprise platform business, including products, customers, and employees, has been acquired by Mirantis, inc., effective 13-November-2019. For more information on the acquisition and how it may affect you and your business, refer to the Docker Enterprise Customer FAQ.
Once you’ve joined multiple DTR replicas nodes forhigh-availability, you can configure your ownload balancer to balance user requests across all replicas.
This allows users to access DTR using a centralized domain name. If a replicagoes down, the load balancer can detect that and stop forwarding requests toit, so that the failure goes unnoticed by users.
DTR exposes several endpoints you can use to assess if a DTR replica is healthyor not:
/_ping
: Is an unauthenticated endpoint that checks if the DTR replica ishealthy. This is useful for load balancing or other automated health check tasks./nginx_status
: Returns the number of connections being handled by theNGINX front-end used by DTR./api/v0/meta/cluster_status
: Returns extensive information about all DTRreplicas.DTR does not provide a load balancing service. You can use an on-premisesor cloud-based load balancer to balance requests across multiple DTR replicas.
Additional load balancer requirements for UCP
If you are also using UCP, there are additional requirements if you plan to load balance both UCP and DTR using the same load balancer.
You can use the unauthenticated /_ping
endpoint on each DTR replica,to check if the replica is healthy and if it should remain in the load balancingpool or not. Ecotect 2011 keygen mac osx.
Also, make sure you configure your load balancer to:
Host
HTTP header correctly.The /_ping
endpoint returns a JSON object for the replica being queried ofthe form:
A response of 'Healthy': true
means the replica is suitable for takingrequests. It is also sufficient to check whether the HTTP status code is 200.
An unhealthy replica will return 503 as the status code and populate 'Error'
with more details on any one of these services:
Note that this endpoint is for checking the health of a single replica. To getthe health of every replica in a cluster, querying each replica individually isthe preferred way to do it in real time.
Use the following examples to configure your load balancer for DTR.
You can deploy your load balancer using:
Sep 02, 2015 The following is an example of using BIG-IP to automate the routing of HTTP and DNS requests for containers across a Docker cluster. The process for connecting Docker to BIG-IP will involve exporting the list of containers that are running on a Docker host and enabling a process to route HTTP and DNS requests to the appropriate Docker container.
This topic applies to Docker Enterprise.
The Docker Enterprise platform business, including products, customers, and employees, has been acquired by Mirantis, inc., effective 13-November-2019. For more information on the acquisition and how it may affect you and your business, refer to the Docker Enterprise Customer FAQ.
Once you’ve joined multiple DTR replicas nodes forhigh-availability, you can configure your ownload balancer to balance user requests across all replicas.
This allows users to access DTR using a centralized domain name. If a replicagoes down, the load balancer can detect that and stop forwarding requests toit, so that the failure goes unnoticed by users.
DTR exposes several endpoints you can use to assess if a DTR replica is healthyor not:
/_ping
: Is an unauthenticated endpoint that checks if the DTR replica ishealthy. This is useful for load balancing or other automated health check tasks./nginx_status
: Returns the number of connections being handled by theNGINX front-end used by DTR./api/v0/meta/cluster_status
: Returns extensive information about all DTRreplicas.DTR does not provide a load balancing service. You can use an on-premisesor cloud-based load balancer to balance requests across multiple DTR replicas.
Additional load balancer requirements for UCP
If you are also using UCP, there are additional requirements if you plan to load balance both UCP and DTR using the same load balancer.
You can use the unauthenticated /_ping
endpoint on each DTR replica,to check if the replica is healthy and if it should remain in the load balancingpool or not. Ecotect 2011 keygen mac osx.
Also, make sure you configure your load balancer to:
Host
HTTP header correctly.The /_ping
endpoint returns a JSON object for the replica being queried ofthe form:
A response of 'Healthy': true
means the replica is suitable for takingrequests. It is also sufficient to check whether the HTTP status code is 200.
An unhealthy replica will return 503 as the status code and populate 'Error'
with more details on any one of these services:
Note that this endpoint is for checking the health of a single replica. To getthe health of every replica in a cluster, querying each replica individually isthe preferred way to do it in real time.
Use the following examples to configure your load balancer for DTR.
You can deploy your load balancer using: