Infrastructure as code (IaC) is the practice of managing and provisioning infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. The IT infrastructure managed by this comprises both physical equipment such as bare-metal servers as well as virtual machines and associated configuration resources. The definitions are stored in a version control system. IaC takes proven coding techniques and extends them to your infrastructure directly, effectively blurring the line between what is an application and what is the environment.
Our focus will be to provide tight integration with best of breed IaC tools, such that all infrastructure related workflows in GitLab are well supported. Our initial focus will likely be on Terraform.
Infrastructure and Application provisioning shouldn't be mixed! Application delivery is covered by our Continuous Delivery directions.
Our vision is to provide several levels of Infrastructure as Code support:
As Infrastructure as Code usage scales across teams collaboration pain points around security, compliance and adopting best practices arise. Traditionally these pain points are solved by written documentation. Modern infrastructure as code applications have implemented Policy as Code tools to enable automated checking of infrastructure definitions against easy to write policy definitions. One prime example of this is Hashicorp's Sentinel.
The principles of Policy as Code are closely aligned with Infrastructure as Code. Within GitLab our existing primitives of integrated CI with CI job definition in-code model similar behavior to modern Policy as Code frameworks. At present our existing CI approach allows easy integration of special Policy as Code tools and GitLab.
We have a dedicated page for Kubernetes management directions. The following directions are related to generic Infrastructure as Code tool support in GitLab.
First, we are going to focus on Terraform support, the de facto standard in infrastructure provisioning. As we are moving Infrastructure as Code support towards Viable, we have a dedicated Epic to collect all our plans.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome!
We are currently looking into customer use-cases around Infrastructure as Code. We would like to hear your use case on the topic. If you would be open to share your setting with us, please reach us to Viktor Nagy.
Even though, we consider our Infrastructure as Code support to be
Minimal at the moment, we see several GitLab customers using our CI/CD capabilities in production environments. Usually, Terraform-focused CI/CD projects are run
as multi project pipelines.
We don't consider GitLab a replacement of IaC tools, rather a complement. Based on several discussions, we consider Terraform being the de facto standard of infrastructure provisioning.
Given the trends around containerization, ephemeral and immutable infrastructures we expect the relevance of configuration management tools to decrease, and infrastructure provisioning to gain more market share.
As already mentioned, we've several customers using IaC solutions with GitLab. The following list shows our primary points of contacts for customer interviews around IaC.