As an engineer, we’ve all been there. In the middle of an escalation, users are frustrated, management is hovering over you looking for updates every 5 minutes, while at the same time you are trying to troubleshoot the issue and figure out what’s going on. It’s a stressful situation to be in, and unfortunately one that we find ourselves in all too often in IT. Everyone just wants it fixed and they want it NOW!
As part of Rancher 2.5, we are excited to introduce a new, simpler way to install Rancher called RancherD. RancherD is a single binary you can launch on a host to bring up a Kubernetes cluster bundled with a deployment of Rancher itself. This means you just have one thing to manage: RancherD. Configuration and upgrading are no longer two-step processes where you first have to deal with the underlying Kubernetes cluster and then deal with the Rancher deployment.
Amazon EKS is the most popular managed Kubernetes solution. DevOps teams can quickly spin up clusters in the cloud and get started with Kubernetes in a few clicks. As organizations embrace Kubernetes in the cloud, the challenge becomes managing clusters across multiple regions or accounts. At that point, organizations struggle to visualize all of their clusters.
Despite the lockdown restrictions of the last six months, I'm delighted to announce that we've released Rancher 2.5 on schedule today. This latest release represents another major milestone of Rancher's "Computing Everywhere" strategy by delivering management capabilities that match the extraordinary popularity of Amazon EKS and our lightweight Kubernetes distribution, K3s.
The ability of Kubernetes to easily deploy and manage containerized software has given organizations tremendous capabilities in their cloud services, with clusters multiplying into the hundreds or thousands and extending out to the edge for any number of purposes. But its growing popularity has also led to challenges in managing complexity in an environment that is conducive to cluster sprawl.
We’ve just launched Cortex 1.4.0, one of the most significant releases of 2020. The big headline: The new blocks storage engine has exited the experimental phase and is now marked as Generally Available. Blocks storage aims to reduce the operational complexity and costs of running a Cortex cluster at scale. In particular, it removes the dependency from a NoSQL database to store series indexes.
I’ve built web applications for 15 years. Some have succeeded and flourished, others have crashed and burned. But I’ve learned some hard-won lessons along the way: techniques that correlate with maintainable code and long-term success. Maybe they can help you.
If you work in Information Technology, you have doubtless encountered logs- in fact depending on your area of expertise, you may be inundated with them on a daily basis. Nearly every piece of digital technology produces some kind of log, from complex web applications to the drivers that power your mouse and keyboard. As such, the definition of what a “log” actually is, is necessarily loose; any output received from a piece of software could be considered a log.
In this article, you will learn how to add inline image scanning to a Google Cloud Build pipeline using the Sysdig Secure DevOps platform. We will show you how to create a basic workflow to build your container image, scan the image, and push it to a registry. We will also customize scanning policies to stop the build if a high-risk vulnerability is detected.
