v0.1.0 (2019-11-05)

Kubeform v0.1.0 comes with various features and bug fixes. Please, try it and give us your valuable feedback. To install, please follow the guide here.

Significant Features

  • Native Kubernetes Support Standard Kubernetes is all you need. If you can run Kubernetes, you can provision and manage cloud infrastructure using Kubeform. Use standard Kubernetes CLI and API to provision and manage different cloud infrastructures. This native integration with Kubernetes means your cloud infrastructures are ready for any higher level deployment tooling like GitOps, Open Policy Agent (OPA), etc.

  • Built on Terraform Terraform is a popular tool for provisioning cloud infrastructure. Kubeform is built on top of Terraform. You can think it like a kubernetes operator for terraform. You can easily convert any resource of terraform using a CRD. You can just write a yaml for the resource which is almost same as a tf configuration. After applying the yaml using kubernetes API, Kubeform will provision the cloud infrastructure for you!

  • Infrastructure as Code: Using Kubeform, you can just write a yaml and provision any cloud infrastructure in popular cloud platforms. You can easily provision and manage cloud infrastructures using codes. You can automate the life cycle of cloud infrastructure using Kubeform.

  • Supports Multiple Cloud Platform: Kubeform supports 5 top cloud platforms. These are AWS, Google Cloud, Azure, Digitalocean and Linode. Using Kubeform, Infrastructure of any of these clouds can be provisioned in a Kubernetes native way.

Fixed bugs

  • Terraform show command doesn’t work #19
  • Fix sensitive info leakage #16
  • unsupported type “float64” #10
  • Naming conflict #9

Closed issues

  • Clean up in generated code #33
  • Add Resource Phase #32
  • Write Docs #30
  • Add installer chart for kfc #29
  • Handle secret naming conflict #27
  • Support TF modules #24
  • Handling state #23
  • Handling Computed field #22
  • mod file #21
  • Change all CRDs to namespaced objects #20
  • Handle tfstate #18
  • Add Provider info #17
  • CRD to Resource name mapping #15
  • Handle field visibility #13
  • Handle MaxItems/MinItems #12
  • Handle optional fields #11
  • Sort generated field by name #8
  • Remove provider_ prefix from type file names #7
  • Use lowerCamelCase for json tag #6
  • Remove Spec from inner structs #5
  • Generate CRD from TF Resource schema #3
  • Use Dynamic client to write controller for generated CRDs #2
  • Design discussion notes #1

Merged pull requests