An upcoming version of the Azure Provider will change the blocks backendpool, backendpoolhealthprobe, backendpoolloadbalancing, frontendendpoint and routingrule from a List to a Set to work around an ordering issue within the Azure API - as such you should update your Terraform Configuration to reference these new Maps, rather than the Lists directly, due to the upcoming breaking change.

For example, changing azurermfrontdoor.example.frontendendpoint1.id to azurermfrontdoor.example.frontendendpointsexampleFrontendEndpoint2 ( 9357 ) azurermlbbackendaddresspool - the field backendaddresses has been deprecated and is no longer functional - instead the azurermlbbackendaddresspooladdress resource offers the same functionality.

As we employ these new features in Terraform, we are looking to build the best possible user experience in the Kubernetes provider.

Get Started Success Support Success Support Customer Success Overview Technical Account Management Implementation Services Enterprise Architecture Support Support Portal Submit A Ticket System Status Technical Support Services and Policies Contact Us Compare Support Plans Unlocking the Cloud Operating Model Read whitepaper Bringing Consul as a service to Azure with Microsoft Learn More Get Pricing Blog Home Products Technology Company HashiCorp Voices All Products Technology Deploy Any Resource With The New Kubernetes Provider for HashiCorp Terraform May 26 2020 Aareet Shermon, Phil Sautter, Alex Somesan We are pleased to announce the alpha release of a new version of the Kubernetes Provider for HashiCorp Terraform.

The kubernetes-alpha provider lets you package, deploy, and manage all Kubernetes resources, including Custom Resource Definitions, using HashiCorp Configuration Language (HCL).

With the addition of the kubernetes-alpha provider, you can now manage the full lifecycle of Kubernetes and its workloads using Terraform.

All Kubernetes resources are accessible through this new provider.

SSA is a new merging algorithm introduced in Kubernetes 1.16.

It will become the default interaction model in a future version of Kubernetes.

With SSA enabled, the provider defers to the Kubernetes API to detect differences in attributes and handle conflict detection for Terraform plan and apply.

A journal of changes is kept in the resource metadata so users can easily determine which attributes have been modified by Terraform as the manager.

By leveraging SSA, Terraform delivers a user experience closer to what Kubernetes users are familiar with and expect from native tools such as kubectl.

Github Terraform Providers Download The Latest

To try out this provider, you will need to download the latest release from the github repository.

Github Terraform Providers Code As Well

Please download both the source code as well as the binary appropriate to your architecture.

We also assume that you have a Kubernetes test environment available to use.

Please ensure that the Kubernetes cluster you choose meets the minimum version requirements (1.17 or newer).

This example will work with clusters created via minikube or kind.

This example will install a Custom Resource Definition (CRD) using the kubernetesmanifest resource available in the new provider.

To try this example out, change directories into the examplescrd folder of the kubernetes-alpha source code that you downloaded earlier.

We will also check that the latest version of Terraform is installed.

In the next section, we describe how you can ease the conversion process of your YAML manifests into the HCL input required by this resource.

A quick check with kubectl shows that the CRD was successfully applied.

This is followed by a final check to ensure the CRD was correctly removed.

We are excited about the possibilities this provider brings and were looking forward to hearing your feedback.

There are a couple of options available to you to automate this conversion.

For YAML manifests containing multiple documents, we recommend creating unique kubernetesmanifest resources in your Terraform configuration for each document.

It relies on new features introduced in Terraform v0.12, such as the rich type system for resource attributes.