Operations | Monitoring | ITSM | DevOps | Cloud

We want to hear directly from you about your experience using Puppet products so we can ensure our portfolio rises to the demand of our customers. Take this survey to share your expertise with us. At Puppet, we’re dedicated to innovating the most modern, easy-to-use, secure and compliant products for our customers to ensure practitioners can simplify their workflows and enterprises can meet their business goals. Your input is extraordinarily valuable to us.

Trying to improve the reliability of your Kubernetes deployment? Start with these 5 chaos experiments. Kubernetes 1.20 is scheduled to be released next week, and this version contains a number of amazing enhancements including graceful node shutdown, more visibility into resource requests, and snapshotting volumes. But the change generating the most buzz is the deprecation of Docker as a container runtime.

If you work in monitoring, you know how important it is for the right people to see the right data. Too much irrelevant data creates a flurry of alerts that hinders productivity, and missing out on key data leads to visibility issues. Worst of all is when you get the wrong people tinkering with data that belongs to other teams.

Cloud-native is the ultimate buzzword lately. So, is “cloud-native storage” just an attempt to grab on to this concept, hoping for a little boost? Actually, there is something more to it, and I’ll unpack that here. The premise of cloud-native storage is simple: its native habitat is a Kubernetes cluster. When we design with the assumption that a technology will exist in Kubernetes, we get to look around and see what functionalities already exist in that system.

On October 1, 2020, the FCC invited comments from the telecommunications industry to ascertain progress on implementing Caller ID Authentication. Verizon’s reply underscored the extensive amount of time and effort its team(s) have put in, yielding substantial progress.

We’ve heard your feedback and are happy to announce that Mattermost will be introducing Collapsed Reply Threads in beta early next year! This feature is a top priority for our team and is the most voted feature request on our idea forum. Threads are core to the messaging experience in Mattermost. They allow users to organize conversations about various topics within a channel.

The internet is changing all aspects of business communication, and with more of us than ever working remotely, it’s a change that is accelerating. Messaging—the ability to synchronously communicate with teams, coordinating work and workflows—is at the center of this new mode of day-to-day business life. The importance of messaging tools—like Slack, Microsoft Teams, and Mattermost—is well-known to those who have already made this shift.

Under the leadership of innovative CIOs—Chief Information Officers—the public sector is blazing new trails and focusing on things like digital transformation to provide constituents with the best services available in the most efficient way possible. While digital transformation will impact the way federal and state agencies look at and adopt new technologies, it will also affect the role of the CIO.

Earlier this year, we launched ChartCenter, our newest community platform to help Kubernetes developers find Helm charts. This new free Helm central repository was built with chart immutability  in mind— meaning every version of a Helm chart and every version in ChartCenter will always be available even if the original source goes down.

Every team has their experts. Maybe you’re the expert for a segment of your team’s applications—the person who’s always called when there’s a problem or when something unexpected happens or when things just look “weird” and the solution isn’t simple. Maybe there’s two of you or even, if you’re lucky, three!