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
Wiktor Niesiobędzki 1a657b31d3 Bump beta provider to 4.48 
This is the first version that supports `gateway_api_config` block
 		2023-01-29 15:50:24 +01:00
..
__need_fixing/onprem Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
coredns Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
cos-generic-metadata Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
envoy-traffic-director Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
mysql Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
nginx Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
nginx-tls Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
simple-nva Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
squid Bump beta provider to 4.48 2023-01-29 15:50:24 +01:00
.gitignore Refactor the onprem module (#55) 2020-04-06 16:27:13 +02:00
README.md Assorted module fixes (#1045) 2022-12-10 15:40:15 +01: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 perfomance 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