We are excited to be making a number of Habitat-related product announcements today at ChefConf 2018. Over the last couple years, our customers have adopted Habitat for two main scenarios: lift, shift, and modernize legacy applications into the cloud or containers, and accelerating adoption of containers for new applications as they move into wider deployment of technologies like Kubernetes. This week’s product announcements have a direct connection to these use cases.
First, we are announcing the general availability of Habitat depot behind the firewall. This helps all Habitat users, but particularly those who have legacy or proprietary business applications that cannot be built and published through the Habitat Builder SaaS. Over the last six months we have been working with a small group of customer development partners to bring this capability to life. You can read more about its features here.
Secondly, we are making a number of announcements related to Habitat integrations into the cloud-native and container ecosystem:
- The newly-updated Habitat Operator for Kubernetes bridges the standard management interface of Habitat services with the Operator model of Kubernetes for container maintenance. It is the recommended way to operate Habitat packages inside Kubernetes and also obviates developers from having to write their own operators for each and every application they deploy into Kubernetes.
- Habitat Builder can now publish directly to Azure Container Registry (ACR) allowing for one-click continuous deployment of even the most sophisticated applications into Azure Kubernetes Service (AKS). We launched this a few weeks ago at Microsoft Build, so you can read more about it here. Be sure to attend our webinar in a couple of weeks where we will demonstrate how Habitat’s build once, run anywhere approach allows you to deliver the same application to Azure Compute Service and AKS with no additional work.
- The Open Service Broker (OSB) standard, originally created by Pivotal, allows you to bridge applications and services running on different clouds and platforms. We’re thrilled to announce a Habitat OSB reference implementation so you can build and ship these packages once, whether they are running on a containerized environment or not.
- Helm chart integration allows you to export your Habitat-built packages into Helm.
- Finally, you can now track Habitat application health using an integration with Splunk’s HTTP Event Collector (HEC).
Habitat at ChefConf
It’s hard to believe that Habitat is not even two years old and yet we have dozens of customers – many of whom are here this week at ChefConf – telling their stories about how Habitat is helping them streamline their development processes and achieve one way to production for applications, no matter what their vintage. You’ll hear many of these stories on the main stage. But don’t miss some of the breakout sessions where customers are sharing practical lessons learned and problems they are solving with Habitat. And, as usual, you can visit habitat.sh to get started with Habitat.