Puppet Labs announced Puppet Enterprise 3.8, with major updates to Puppet Node Manager and a new Puppet App, Puppet Code Manager.
These new capabilities represent the next step of infrastructure as code by providing robust provisioning capabilities for Docker containers, AWS infrastructure and bare metal. Additionally, with the new Puppet Code Manager, organizations can speed the deployment of infrastructure changes in a testable and programmatic way.
“Businesses are adopting DevOps tools and practices because they are under tremendous pressure to deliver new and reliable services faster, across an ever-expanding set of infrastructure technologies, “ said Nigel Kersten, CIO of Puppet Labs. “By adding support for Docker, AWS and bare metal, Puppet Enterprise 3.8 makes it faster and easier to provision and manage nearly any infrastructure technology. Now, IT teams can focus less time on managing change, and more time driving change throughout their organizations.”
Puppet Node Manager, released late last year, initially included a rules-based method to organize servers based on key characteristics, such as application, role, data center, operating environment, and geographic location. With Puppet Enterprise 3.8, Puppet Node Manager includes capabilities for automating the provisioning of infrastructure, from containers to bare metal. Puppet Node Manager makes it faster to get new systems online by automating initial provisioning, along with the key tasks required to make new infrastructure production-ready. By reducing the friction along the way, provisioning time can be reduced from days or weeks to minutes, so IT ops teams spend less time on manual and time-consuming tasks, and more time delivering innovation and value.
With support for Docker, Amazon Web Services (AWS) and bare metal environments, Puppet Labs eliminates the complexity associated with provisioning and managing infrastructure across a heterogeneous environment.
- Containers – A new Puppet Supported module for Docker makes it possible to manage the Docker Platform and launch Docker containers in Puppet-managed infrastructure. For teams that rely on containers to simplify application deployments, these new capabilities help avoid configuration issues with the Docker daemon running those containers. The result is that those teams spend less time troubleshooting configuration issues and more time developing and deploying better apps.
- Cloud environments – The new AWS module allows organizations to provision, configure, and manage AWS resources in a consistent and repeatable manner. The module supports the following AWS services: EC2, Virtual Private Cloud (VPC), Elastic Load Balancing, Auto Scaling, Security Groups and Route53. Since these new capabilities work alongside Puppet Enterprise’s ability to manage packages, services and other host resources, organizations can describe their virtual network, launch AWS instances and then manage the software on those instances — all using Puppet Enterprise.
With a shared language and a simple interface to common AWS resources, the AWS module allows familiar practices such as code review and continuous integration to be applied to the composition of machines and networks in AWS. This gives organizations the benefits of infrastructure as code along with their mature change control process.
- Bare metal – As part of this release, Razor, Puppet Labs' bare-metal provisioning tool, moves from tech preview to a generally available, fully supported set of capabilities. Razor includes the ability to automatically discover bare-metal hardware, dynamically configure OS and/or hypervisors and hand off resources to Puppet Enterprise for workload configuration via policy-based automation. This significantly reduces the lead time for provisioning and configuring a new machine, and enables customers to get to day-two operations without manual intervention. Razor provides policy-driven bare-metal provisioning for a variety of Linux and Windows operating systems, as well as VMware's ESXi.
Puppet Code Manager, based on the popular r10k technology, is the newest Puppet App, and a step towards realizing the benefits of infrastructure as code. Puppet Enterprise users define their infrastructures in Puppet code, and then Puppet Code Manager helps manage that code as it moves through all development and testing environments to production deployment. With Puppet Code Manager, IT Ops are able to increase reliability with a consistent and automated way of changing, reviewing, testing, and promoting the Puppet code used to define their infrastructure.
Puppet Code Manager integrates easily with Git for version control, giving users all the benefits of Git: peer review using pull requests; code promotion to successive deployment tiers by merging branches; a full change history and more. Combined with other Puppet Labs technologies such as Beaker, and Jenkins for acceptance testing, Puppet Code Manager allows teams to apply continuous delivery practices to the Puppet code that defines their infrastructure.
Both Puppet Enterprise 3.8 (including the next-generation Node Manager, Razor and Puppet Code Manager) and the Puppet Supported module for Docker will be generally available in late April. The AWS module is now available on the Puppet Forge.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.