puppetlabs/vmpooler-provider-gce
2
0
Fork 0
mirror of https://github.com/puppetlabs/vmpooler-provider-gce.git synced 2026-01-26 03:18:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Adding the cloud DNS API library and related methods

Browse source 
we setup DNS when a VM is created and tear it down when a VM is deleted
the DNS zone should exist already and is referenced by a provider setting
the dns zone is also set in order to use it for vm_ready? instead of the global
domain
instances have a label that identifies which project they belong to, so
it can be used for FW rules
This commit is contained in:
Samuel Beaulieu 2021-12-29 08:13:32 -06:00
parent f6ec318b2d
commit daa55fe5b8
No known key found for this signature in database
GPG key ID: 12030F74136D0F34
9 changed files with 167 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

7
vmpooler.yaml.example
View file

@ -72,6 +72,13 @@
# - network_name
# The GCE network_name to use
# (required)
# - dns_zone_resource_name
# The name given to the DNS zone ressource. This is not the domain, but the name identifier of a zone eg example-com
# (optional) when not set, the dns setup / teardown is skipped
# - dns_zone
# The dns zone domain set for the dns_zone_resource_name. This becomes the domain part of the FQDN ie $vm_name.$dns_zone
# When setting multiple providers at the same time, this value should be set for each GCE pools.
# default to: global config:domain. if dns_zone is set, it overwrites the top-level domain when checking vm_ready?
# Example:
:gce: