zecfoundation
/
cloud-foundation-fabric
mirror of https://github.com/ZcashFoundation/cloud-foundation-fabric.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cloud-foundation-fabric/modules/cloud-config-container
History
Ludovico Magnocavallo 789328ff5a
Bump provider versions to v5.0.0 (#1724) 
* bump provider versions to 5.0.0

* fix cloud run, logging and vpc-sc

* Fix secret manager

* fix gke nodepool

* fix gke multitenant stage and blueprint

* Moving alloydb module to experimental.

* Add project to bare resources in examples

* tfdoc

* fix svpc blueprint test

* Revert "fix svpc blueprint test"

This reverts commit 14f02659098070136e64ead600580dd52c23c339.

* Fix GKE peering project

* Disable tests in alloydb module

* Bring back secret ids in secret manager tests

* Remove duplicate key

* last push

---------

Co-authored-by: Julio Castillo <jccb@google.com>
 		2023-10-03 12:15:36 +00:00
..
__need_fixing/onprem Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
coredns Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
cos-generic-metadata Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
envoy-traffic-director Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
mysql Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
nginx Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
nginx-tls Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
simple-nva Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
squid Bump provider versions to v5.0.0 (#1724) 2023-10-03 12:15:36 +00:00
.gitignore Refactor the onprem module (#55) 2020-04-06 16:27:13 +02:00
README.md Several updates 2023-05-13 23:51:46 -04:00

README.md

Instance Configuration via cloud-config

This set of modules creates specialized cloud-config configurations, which are designed for use with Container Optimized OS (the onprem module is the only exception) but can also be used as a basis for other image types or cloud providers.

These modules are designed for several use cases:

  • to quickly prototype specialized services (eg MySQL access or HTTP serving) for prototyping infrastructure
  • to emulate production services for performance testing
  • to easily add glue components for services like DNS (eg to work around inbound/outbound forwarding limitations)
  • to implement cloud-native production deployments that leverage cloud-init for configuration management, without the need of a separate tool

Available modules

Using the modules

All modules are designed to be as lightweight as possible, so that specialized modules like compute-vm can be leveraged to manage instances or instance templates, and to allow simple forking to create custom derivatives.

To use the modules with instances or instance templates, simply set use their cloud_config output for the user-data metadata. When updating the metadata after a variable change remember to manually restart the instances that use a module's output, or the changes won't effect the running system.

TODO

  • convert all xxx_config variables to use file content instead of path