FormKube uses the Terraform Azure Remote State Backend azurerm to store its state.
It is mandatory to work with the azurerm backend. Local statefiles are not supported anymore in FormKube >= 3.0.0.
For more information on Terraform Remote State Backends, please refer to the official Docs.
The creation of the Azure Remote State Backend can be done with FormKube:
bash ./scripts/create_backend.sh
The configuration of the Azure Storage Account and Azure Storage Container will be auto-generated using the vars defined in the vars.tf of the cluster:
backend_resourcegroup_name="samplecluster-prd.example.comFormKubeState"`
backend_storageaccount_name="samplecluster-prd.example.com"
backend_storagecontainer_name="samplecluster-prd.example.com"
In the background, FormKube will generate a backendconfig inside clusters/$FORMKUBE_CLUSTER/backendconfig which will then later be used when applying the cluster.
It is also possible to use an existing Azure Storage Account and Azure Storage Container as remote backend. To do so, simply put your configuration inside clusters/$FORMKUBE_CLUSTER/backendconfig and skip above step to create the backend.
Exemplary backendconfig's can be found in the clusters folder inside this repo.
NOTE: FormKube authenticates itself with the backend using the Service Principal you provide it to run terraform. Please ensure that the Service Principal has the correct permissions to access the Azure Storage Account and Azure Storage Container and that the Tenant ID and Subscription ID match.
Deleting the backend Azure Storage Account and Azure Storage Container can be done with FormKube:
bash ./scripts/delete_backend.sh
Important: Running ./scripts/destroy.sh does not include deleting the backend.