system-config/playbooks/templates/clouds
Clark Boylan ffcd1791bf Cleanup nodepool builder clouds.yaml
We ended up running into a problem with nodepool built control plane
images (has to do with boot from volume not allowing us to delete images
that are in use by a nova instance). We have decided to clean this up
and go back to not doing this until we can do it more properly.

Note this isn't a revert because having a group for access to control
plane clouds does seem like a good idea in general and I believe there
have been changes we'd have to resolve in the clouds.yaml files anyway.

Depends-On: https://review.opendev.org/#/c/665012/
Change-Id: I5e72928ec2dec37afa9c8567eff30eb6e9c04f1d
2019-07-22 13:55:29 -07:00
..
bridge_all_clouds.yaml.j2 Use qcow2 images on fortnebula 2019-07-02 14:09:12 -07:00
bridge_clouds.yaml.j2 Use qcow2 images on fortnebula 2019-07-02 14:09:12 -07:00
bridge_kube_config.yaml.j2 Configure .kube/config on bridge 2019-02-06 15:43:19 -08:00
nodepool_builder_clouds.yaml.j2 Use qcow2 images on fortnebula 2019-07-02 14:09:12 -07:00
nodepool_clouds.yaml.j2 Cleanup nodepool builder clouds.yaml 2019-07-22 13:55:29 -07:00
nodepool_kube_config.yaml.j2 Update the current-context to valid context 2018-11-30 15:00:08 -06:00