Operations | Monitoring | ITSM | DevOps | Cloud

I’m pleased to share that G2, the world’s largest and most trusted tech marketplace, has recognized our solutions in its 2023 Winter Report. We received a total of 15 badges across our business units for Rancher, SUSE Linux Enterprise Server (SLES), SLE Desktop and SLE Real Time – including the Users Love Us badge for all products – as well as three badges for the openSUSE community with Leap and Tumbleweed.

To get the best performance out of your Kubernetes cluster, SREs and software engineers must have enough knowledge and instruments to find misconfiguration and bottlenecks. At the same time, thanks to Kubernetes’ ever-growing popularity, there is a global shortage of expertise on the platform.

The deployment of Ruby on Rails and Rack frameworks is embedded in Cloud 66’s DNA, but we are always interested to see other Ruby frameworks becoming popular, and happy to support developers who prefer to use them instead of Rails. In this post, we’re going to show you how easy it is to deploy a Hanami Ruby application on AWS cloud with Cloud 66. The recent Hanami v2.0 release brought a lot of incremental upgrades to the framework, which made it more mature.

A neatly setup access control telling which user can do exactly what on an incident management platform can save a lot of time and hassle in the future. In the past, Spike.sh had only 2 roles - Admin and Member. The only difference in these roles were that only Admins can remove members. It was fairly simple and most users liked it. However, with larger teams coming onboard, it gets a little difficult to control for admins. So, we have empowered the existing system by adding two more roles.

How to set Service Level Objectives with 3 steps guide.

No matter what application you’re building and who your target customers are, everyone can agree that it’s critical to avoid broken deployments. To aid in this goal, many tools and concepts have been invented, with Kubernetes preview environments being one of them. In this post, you’ll get a deeper understanding of how preview environments work, how organizations are using them, and how you can get started yourself.

A security bill of material (SBOM) is an inventory of the entire building components of a software application. These components include open source libraries, dependencies, commercial components, licenses, patch status, version information, upgrades available, CVEs, etc. Having an SBOM of a codebase or piece of software provides deep visibility into core components that help quickly identify and mitigate the security and licensing risks associated with the software supply chain.

As we get ready to wish the term SASE a happy 4th birthday, it seems odd that there is still a great deal of confusion in the market about what SASE really is and how it relates to a ‘Zero Trust’ architecture. For many, SASE is a framework for secure network design; for others, it’s seen more as an architectural approach to delivering Zero Trust. So why do we have this confusion when Gartner defined SASE back in 2019?