Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes, commonly called K8s, is an open-source container management system developed by Google. Containers and tools like Kubernetes enable automation of many aspects of application deployment, which provides tremendous benefits to businesses. K8s is just as vulnerable to attacks and cybercrime as traditional environments, in both public and private clouds. In this blog post, we’ve compiled everything you need to know to make sure your Kubernetes environment is safe.

Chef and Puppet are two popular tools for configuration management. These type of tools help engineers to maintain a consistent configuration in all servers. For instance, all servers might need to have IIS with a binding to port 443 for HTTPS access and the respective firewall rule for inbound traffic. More importantly, if anyone removes the firewall rule, these type of tools will keep consistency by creating the firewall rule again.

By Des Nnochiri Most enterprises now use two or more cloud service providers, and 35% use up to five monitoring tools to keep tabs on hybrid cloud and multi-cloud environments. Even before organizations began shifting software and IT infrastructure to the cloud, a typical business would use four to ten tools just to monitor and troubleshoot their internal networks, according to analyst and consulting firm Enterprise Management Associates.

Recently, we ran into a problem where a customer’s dashboard broke to such an extent that it hung on loading. This is a really rare problem and in this case was an instance where the customer had created a variable that referenced itself. Once the dashboard is broken in this way, it is impossible to reach a screen allowing you to remove that variable. This post is not about how it was broken, but about how we resolved the error.

Opsgenie was built by real people who truly understood the pain of on-call, alert fatigue, and collaboration roadblocks. We empower our customers to resolve incidents faster by leveraging the tools they already use. As part of our mission to keep your always-on services up and running, we’ve worked with three key partners to strengthen the integrations we offer. It’s important that during an incident you can use the tools you’re accustomed to.

We live in a digital world, and it’s becoming more and more apparent every day. We rely on our smartphones to give us directions to where we need to go. We rely on email to share information with our colleagues, family and friends. We access our medical records through online portals. We even hail a rideshare through an app that connects us to drivers in locations across the globe.

Read the details on what's new in the design and we have news on 4 more StatusHub feature updates.

IBM Cloud has made a massive shift to Kubernetes. From an initial plan for a hosted Kubernetes public cloud offering it has snowballed to tens of thousands of production Kubernetes clusters running across more than 60 data centers around the globe, hosting 90% of the PaaS and SaaS services offered by IBM Cloud. I spoke with Dan Berg, IBM Distinguished Engineer, to find out more about their journey, what triggered such a significant shift, and what they learned along the way.

When PagerDuty’s VP of Product Management Rachel Obstler announced the beta version of our new Slack integration in April in her “Anticipating, Monitoring, and Managing Incidents via Slack” panel at Slack Frontiers, we expected significant interest in the integration among our customers.

I was reminiscing about an incident that happened at a past job with an old co-worker. You know the one, the one where you installed a library that makes some task of yours simple, only to reveal the library makes things worse. This incident in particular involved the way that images served out of our Ruby on Rails application, and the library that made it possible to “easily resize before serving” them.