Operations | Monitoring | ITSM | DevOps | Cloud

Codefresh

Helm 3: Navigating to Distant Shores

Since its initial debut 5 years ago Kubernetes has grown up quite a bit, but one thing hasn’t changed: writing Kubernetes manifest files from scratch is hard. In fact, it’s borderline discouraging for new users looking to use the defacto container orchestrator. Thus, the need for a package manager was born: Helm. Helm is almost as old as Kubernetes (it’s about 4 years) old and Helm 2 is a merger of two code bases, which made for some interesting ways of approaching even the most basic of security concerns (say, RBAC for instance). If you’re familiar with Helm you already know how useful it is, but there are features you’d like added, some updates you’ve wished for, and a major component you’d like removed: Tiller.

Crafting the perfect Java Docker build flow

What is the bare minimum you need to build, test and run your Java application in Docker container? The recipe: Create a separate Docker image for each step and optimize the way you are running it. I started working with Java in 1998, and for a long time, it was my main programming language. It was a long love–hate relationship. During my work career, I wrote a lot of code in Java. Despite that fact, I don’t think Java is usually the right choice for microservices.

Calling Codefresh pipelines from Github actions

At Codefresh we are all about collaboration and reusing existing standards instead of implementing proprietary solutions. A Codefresh pipeline is based on a series of Docker containers that act as individual steps. All Codefresh plugins are also just Docker images which means that extending a Codefresh pipeline is the same thing as writing a Dockerfile. Github has recently announced an integrated automation solution called Actions.

CI/CD for Microservices Best Practices on DevOps.com

You have finally split your big monolith into microservices. Now what? How do you validate a more complex application? And how do you make it scale? Instead of having one CI/CD pipeline, you have multiple. And as the number of microservices increases so does the number of pipelines. Managing pipelines for microservice applications can quickly get out of hand, especially when you try to reuse common pipeline parts between different applications.

Why you should be using Multi-Stage Docker Builds in 2019

Docker multi-stage builds were announced 2 years ago, but sadly not all developers are using them. Using multi-stage builds can result in a much more secure and smaller Docker image. In some cases, you can take a Docker image from 700MB to 20MB, which makes a big difference in the context of CI/CD. In this webinar, we will see how to use multi-stage Docker builds and the best practices around them.