Operations | Monitoring | ITSM | DevOps | Cloud

I was speaking with a VP of Engineering friend at last year’s KubeCon about how to pitch Kubernetes to the C-Suite. The benefits for innovation were clear - containerized microservices empowered her small teams to deliver more value, more rapidly. As is often the case with Boardroom discussions, though, the question of cost was always next. Sure, they want you to innovate - as long as it’s within the constraints of a budget! But cost discussions around Kubernetes can be difficult.

Minimizing costs, reducing risk, and maximizing business value—all at the same time—requires a delicate balancing act. It’s not a new challenge, nor is it unique to IT infrastructures. But when it comes to the cloud, especially in hybrid cloud scenarios, it requires you to understand the performance, risk/compliance, and cost impacts of your current resource allocations and then adjust to maintain the optimal decisions to meet your SLA and budget targets.

Today we released updates for a series of vulnerabilities termed ‘There’s a hole in the boot’ / BootHole in GRUB2 (GRand Unified Bootloader version 2) that could allow an attacker to subvert UEFI Secure Boot. The original vulnerability, CVE-2020-10713, which is a high priority vulnerability was alerted to Canonical in April 2020.

Deploying a new feature to production is a momentous occasion. It's important to ensure that everything goes properly at this stage, as deployments tend to be error-prone when not handled correctly. To examine why this is and how you can avoid it, let's take a look at the different types of deployments available and where some of them fall short.

In their presentation at the swampUp 2020 conference, IT service manager Marija Kuester and her team at Siemens AG revealed how they use JFrog Artifactory to deploy and scale their Inner Source Hub service, and meet the challenging needs of their key business stakeholders. In the recorded session, the Siemens team outlined the service architecture with rich insights into the IT service deployment and internal developer adoption.

Without SRECon happening this year and the world turned upside down from COVID-19, we set out to hold a virtual event to bring SREs together to share their experiences of what has changed. Last week’s SRE from Home was exactly that. With 1900 registrants, 20 lively Slack channels, six illuminating and entertaining talks from a diverse range of experts in the field and our #askanSRE panel answering attendees’ questions with a candid generosity, it was an amazing, jam-packed day.

Deploying a new feature to production is a momentous occasion. It's important to ensure that everything goes properly at this stage, as deployments tend to be error-prone when not handled correctly. To examine why this is and how you can avoid it, let's take a look at the different types of deployments available and where some of them fall short.

Kubernetes is the most popular Open Source technology of the last five years. It was created by Google to allow companies to use container (Docker) applications in production. Today, Kubernetes is the new standard for running applications in the Cloud or on its servers (on-premise). I even heard from a Cloud architect from Azure: "our customers no longer come to us to do Cloud, but to do Kubernetes". That's to say how much a utility software* upsets a whole ecosystem.