Bridle - Terraform remote backend in Kubernetes
a project by nroberts
Updated over 3 years ago. 3 hacker ♥️. 9 followers.

Project Description

Terraform's remote backend requires a Terraform Cloud account and has an initial limited offering. While the initial offering is suitable for small resource management and teams this quickly becomes an issue as usage demands increase. In addition Terraform's remote operations (plan,apply, etc) are executed on HashiCorp's cloud resources which present issues for sensitive data such as passwords and access keys. Users are also constrained to as what tooling is available on the remote execution environment for example having kubectl as part of a local-resource. This project aims to address these shortcomings in a native Kubernetes implementation.

Goal for this Hackweek

  • Have remote plan and apply operations execution handled in Kubernetes
  • State management: locking and storage
  • Logging: execution output (plan and apply)
  • User interface: view execution output and approve apply operations
  • Helm chart for deploying project

Stretch Goals

  • Trigger plan on Github PR

Implementation

We hope to take the rancher terraform-controller and add a REST API to it to speak Terraform Cloud (sometimes called tfe or terraform enterprise in their docs). We should be able to deploy the controller and write HCL with a backend remote hostname to this new API and run terraform plan/apply from your desktop and use resources in your k8s cluster.

Resources

Join this project

Looking for hackers with the skills:

terraform kubernetes

This project is part of:

Hack Week 20

Activity

  • over 4 years ago: ckim joined this project.
  • over 4 years ago: wgodfrey joined this project.
  • over 4 years ago: moio liked this project.
  • over 4 years ago: hbarnes joined this project.
  • over 4 years ago: luthermonson liked this project.
  • over 4 years ago: rkirkpatrick joined this project.
  • over 4 years ago: nroberts liked this project.
  • over 4 years ago: luthermonson joined this project.
  • over 4 years ago: nroberts joined this project.
  • over 4 years ago: cluse started this project.
  • over 4 years ago: nroberts added keyword "kubernetes" to this project.
  • over 4 years ago: nroberts added keyword "terraform" to this project.
  • over 4 years ago: nroberts originated this project.


    • Comments

    • moio
      over 4 years ago by moio | Reply

      Out of curiosity, how did this project go?

    Similar Projects

    terraform-provider-feilong by e_bischoff

    Project Description

    People need to test operating systems and applications on s390 platform.

    Installation from scratch solutions include:

    • just deploy and provision manually add-emoji (with the help of ftpboot script, if you are at SUSE)
    • use s3270 terminal emulation (used by openQA people?)
    • use LXC from IBM to start CP commands and analyze the results
    • use zPXE to do some PXE-alike booting (used by the orthos team?)
    • use tessia to install from scratch using autoyast
    • use libvirt for s390 to do some nested virtualization on some already deployed z/VM system
    • directly install a Linux kernel on a LPAR and use kvm + libvirt from there

    Deployment from image solutions include:

    • use ICIC web interface (openstack in disguise, contributed by IBM)
    • use ICIC from the openstack terraform provider (used by Rancher QA)
    • use zvm_ansible to control SMAPI
    • connect directly to SMAPI low-level socket interface

    IBM Cloud Infrastructure Center (ICIC) harnesses the Feilong API, but you can use Feilong without installing ICIC, provided you set up a "z/VM cloud connector" into one of your VMs following this schema.

    What about writing a terraform Feilong provider, just like we have the terraform libvirt provider? That would allow to transparently call Feilong from your main.tf files to deploy and destroy resources on your system/z.

    Other Feilong-based solutions include:

    • make libvirt Feilong-aware
    • simply call Feilong from shell scripts with curl
    • use zvmconnector client python library from Feilong
    • use zthin part of Feilong to directly command SMAPI.

    Goal for Hackweek 23

    My final goal is to be able to easily deploy and provision VMs automatically on a z/VM system, in a way that people might enjoy even outside of SUSE.

    My technical preference is to write a terraform provider plugin, as it is the approach that involves the least software components for our deployments, while remaining clean, and compatible with our existing development infrastructure.

    Goals for Hackweek 24

    Feilong provider works and is used internally by SUSE Manager team. Let's push it forward!

    Let's add support for fiberchannel disks and multipath.

    Possible goals for Hackweek 25

    Modernization, maturity, and maintenance.