Align documentation, move glb blueprint (#921)
* aling documentation, move glb blueprint * modules README, sort modules * reorder modules * fix bp links * fix moved blueprint test * use a single cloud shell image in the repo
This commit is contained in:
committed by
GitHub
parent
39f76b3d4c
commit
ed9fd6b08d
@@ -1,20 +1,17 @@
|
||||
# Nginx-based reverse proxy cluster
|
||||
|
||||
This blueprint shows how to deploy an autoscaling reverse proxy cluster using Nginx, based on regional
|
||||
Managed Instance Groups.
|
||||
This blueprint shows how to deploy an autoscaling reverse proxy cluster using Nginx, based on regional Managed Instance Groups.
|
||||
|
||||

|
||||
|
||||
The autoscaling is driven by Nginx current connections metric, sent by Cloud Ops Agent.
|
||||
The autoscaling is driven by Nginx current connections metric, sent by Cloud Ops Agent.
|
||||
|
||||
The example is for Nginx, but it could be easily adapted to any other reverse proxy software (eg.
|
||||
Squid, Varnish, etc).
|
||||
The example is for Nginx, but it could be easily adapted to any other reverse proxy software (eg. Squid, Varnish, etc).
|
||||
|
||||
## Ops Agent image
|
||||
|
||||
There is a simple [`Dockerfile`](Dockerfile) available for building Ops Agent to be run
|
||||
inside the ContainerOS instance. Build the container, push it to your Container/Artifact
|
||||
Repository and set the `ops_agent_image` to point to the image you built.
|
||||
There is a simple [`Dockerfile`](Dockerfile) available for building Ops Agent to be run inside the ContainerOS instance. Build the container, push it to your Container/Artifact Repository and set the `ops_agent_image` to point to the image you built.
|
||||
|
||||
<!-- BEGIN TFDOC -->
|
||||
|
||||
## Variables
|
||||
|
||||
Reference in New Issue
Block a user