Expanding platform engineering capabilities with Radius Resource Types
Now, with Radius Resource Types, platform engineers can define resource types specific to their organizations.
Now, with Radius Resource Types, platform engineers can define resource types specific to their organizations.
With this practical guide, you now know how to secure your Kubernetes cluster using the structured-authentication feature, offering flexible integration with any JWT-compliant token provider.
As the requirements and software surrounding Kubernetes clusters grow along with the required number of clusters, the administrative overhead becomes overwhelming and unsustainable without an appropriate architecture and supportive tooling.
On behalf of HashiCorp and Microsoft, I am excited to announce the release of version 2.0 of the Azure Provider for Terraform. Version 2.0 is a major version upgrade that incorporates a number of features that customers have been asking for, as well as a whole host of smaller but impactful changes.
Last year at Microsoft Connect and DockerCon we announced the Cloud Native Application Bundle (CNAB) specification in partnership with Docker, HashiCorp, and Bitnami. Since then the CNAB community has grown to include Pivotal, Intel, Datadog, and others, and we are all extremely pleased to announce that the CNAB core 1.
There have already been two Terraform Azure provider releases in April and this blog post highlights the new and updated resources in these releases. Before talking about all of the great new functionality, I would like to start by thanking all of the external contributors to the AzureRM provider for these releases.
There is a new release of the AzureRM provider fresh off of the presses. Version 1.23 has lots of new resources and data sources. If you want to get into the nitty-gritty details of the release, check out the Change Log for the provider within the GitHub repo.
In order to provide more clarity into what’s changed in each Terraform AzureRM provider release, we’re kicking off a blog series that will provide the highlights for each release. We will continue to provide details on every release in the Change Log for the provider within the GitHub repo as well.
We want to give a heads-up to Azure customers who are using Terraform to provision and manage MySQL and/or PostgreSQL. As planned, the Azure data team will deprecate their ‘2017-04-30-preview’ API for both MySQL and PostgreSQL on December 1, 2018.
This article will show how to build a blog (or any other static content) using a very popular JAMstack (GatsbyJS, GraphQL, Markdown) and host it on static website hosting for Azure Storage, which provides a cost effective and scalable solution for hosting static content and JavaScript code.
For those who might be wondering what HashiCorp Terraform is, Terraform is a tool which enables workflows for operators to provision and manage Azure infrastructure using “Infrastructure as Code.” For a good overview, check out this introduction to Terraform.
This is part 2 of a 2-part series on CI/CD for “infrastructure as code” on Azure. In part 1, we covered a basic pipeline building application and provisioning infrastructure codified as Terraform templates and Ansible playbooks.
This is part 1 of a 2-part series demonstrating how to continuously build and deploy Azure infrastructure for the applications running on Azure. The first article will show how open source tools, such as Terraform and Ansible, can be leveraged to implement Infrastructure as Code.