-
Notifications
You must be signed in to change notification settings - Fork 14
Module Organization
This document will be updated with plans regarding how to break up kube-metal into various modules; where they will live, how they interact, and such.
The high-level goal of this reorganization is to make the code put into kube-metal thus far usable with any number of providers and other modules. First priority is to support both bare-metal (via matchbox) in addition to Packet.
I like the name kube-metal, and it should probably stay around in some capacity. However the new official Terraform Module Registry has made me change course because they require a name in the form of terraform-PROVIDER-MODULE. So kube-metal as a standalone module is probably not the path forward.
My tentative plan is to host provider-agnostic modules in this repo. That is, modules that are lower level and don't have a good case for being added to the Terraform Module Registry. They will instead be the building blocks for higher level modules (think terraform-packet-kubernetes).