We ran into an issue while applying our Terraform infrastructure on a M1 Mac where we were making use of the Terraform Provider Template.
When applying it, we were getting the following error:
template v2.2.0 does not have a package available for your current platform, darwin_arm64 Since the provider is archived, we need to find an alternative.
What does archiving mean? Per Terraform Archiving Providers documentation.
The code repository and all commit, issue, and PR history will still be available. Existing released binaries will remain available on the releases site. Documentation for the provider will remain on the Terraform website. Issues and pull requests are not being monitored, merged, or added. No new releases will be published. Nightly acceptance tests may not be run. So what alternatives do we have instead of the deprecated provider?
This article applies to: Helm v3.8.0
Helm helps you manage Kubernetes applications â Helm Charts help you define, install, and upgrade even the most complex Kubernetes application. More details on Helm and the commands can be found in the official documentation.
Assuming you use Helm to handle your releases, you might end up in a case where the release will be stuck in a pending state and all subsequent releases will keep failing.
This article applies to Terraform v1.1.4
When using Terraform to manage your infrastructure you will end up in the situation when you want to remove some resources.
You can do this in several ways, but most of the time you can also just remove the Terraform configuration by commenting it out the code, or removing the calling of the module, run terraform apply and it will get rid of the resources.
This article applies to Kubernetes v1.15 and above.
Kubernetes, also known as K8s, is an open-source system for automating the deployment, scaling, and management of containerized applications.
It groups containers that make up an application into logical units for easy management and discovery. But what if something happens to the container? In this case, you might need a quick and easy way to restart it.
Kubernetes Pods usually run until there is a new deployment that will replace them. Therefore, there is no straightforward way to restart a single pod.
In our current environment we have Kong as our Ingress controller in front of our applications.
We are also using the Kong CORS Plugin to enable browsers to make cross-origin requests to our application’s backend. The CORS plugin lets you configure the API gateway behavior to support Cross-Origin Resource Sharing (CORS). If you want to dig deeper into what CORS is, please check the CORS glossary link.
We also make use of helm charts to handle our deployment.
