Operations | Monitoring | ITSM | DevOps | Cloud

Installing Artifactory on GKE, or on any Kubernetes cluster for that matter, can be complex. You have to think through several scenarios, switch back and forth between UI and command line, create a lengthy Helm command, search for acceptable parameters … and so on. All this before you have to configure certificates, licenses, database settings, node settings. But there’s more, what about future proofing it?

Red Hat OpenShift and JFrog Artifactory are a smooth fit together for cloud native, containerized software development at enterprise scale. With the new availability of OpenShift operators certified for JFrog Enterprise, that fit now fastens tight.

Microsoft Azure is a cloud computing platform for building, deploying, and managing global-scale applications. With a wide range of offerings, including dozens of different services, Azure provides tools for users to create large and sophisticated systems for hosting any type of workload. But with the huge number of configuration options and resource types, understanding the health and performance of your applications in Azure can be challenging.

At Taloflow, we are determined not to be the cobbler whose children went barefoot. We approach our own AWS costs as if we are helping one of our customers. The results are striking and worth sharing. And, with zero upfront or reserved commitments required! This post illustrates how a little bit of diligence and a clear cost objective can end up making a large impact on profitability.

Under the hood, the HAProxy Data Plane API and the HAProxy Kubernetes Ingress Controller are powered by a shared set of Go libraries that apply changes to an HAProxy configuration file. In this talk, Marko Juraga describes how these libraries are developed and invites you to use them in your own projects when you need to integrate with HAProxy. Watch Marko’s presentation video or read the transcript below. Explore more HAProxyConf 2019 talks in our User Spotlight Series.

My name is Kat Cosgrove, and I’m a Developer Advocate at JFrog. Before that, I was an engineer on JFrog’s IoT team. Our goal is to bring DevOps to the edge, because it shouldn’t be as difficult to update these kinds of devices as it currently is. In pursuit of this goal, we found a lot of interesting solutions that we could bring into a CI/CD pipeline for embedded Linux devices, and eventually built a rather flashy proof of concept that put several of these solutions on display.

DevOps pipelines enable teams to implement continuous software development processes, often by using automation and collaboration tooling. The overall goal is to quickly release software products, updates, and fixes. To ensure a DevOps pipeline works well, teams add management and monitoring tooling to the pipeline. This includes incident alert management, which supports the team’s efforts in monitoring the security of various software and environment components.

Software Engineering is hard. As time has progressed, the number of languages, frameworks and packages available has grown to the point where it’s rare nowadays to find a project that is developed entirely in a single language or within a single ecosystem. A typical project uses the best languages and frameworks for the job, and these frequently differ depending on what part of the project is being developed.

Hybrid cloud and multi-cloud are two exclusive terms that are often confused. While the hybrid cloud represents a model for extending private cloud infrastructure with one of the existing public clouds, a multi-cloud refers to an environment where multiple clouds are used at the same time, regardless of their type. Thus, while the hybrid cloud represents a very specific use case, multi-cloud is a more generic term and usually better reflects reality.