Use a route table with separate (rather than inline) routes

* Allow users to extend the route table using a data reference
and adding route resources (e.g. unusual peering setups)
* Note: Internally connecting AWS clusters can reduce cross-cloud
flexibility and inhibits blue-green cluster patterns. It is not
recommended
This commit is contained in:
Dalton Hubble
2020-02-25 23:12:19 -08:00
parent f4d260645c
commit 3250994c95
4 changed files with 42 additions and 20 deletions

View File

@ -9,6 +9,7 @@ Notable changes between versions.
#### AWS
* Fix `worker_node_labels` for setting initial worker node labels on Fedora CoreOS ([#651](https://github.com/poseidon/typhoon/pull/651))
* Allow VPC route table extension via reference ([#654](https://github.com/poseidon/typhoon/pull/654))
#### Google Cloud