DevOps

At re:Invent, AWS introduced the ability to have EKS run pods on AWS Fargate, and Fargate is cheaper than hosting Kubernetes yourself. In the last post I created an EKS cluster, so let’s add this new capability to the cluster and remove the need to manage or provision infrastructure for our pods.

Building a Kubernetes cluster is hard, so why not use a managed Kubernetes service? In the previous post I added subnets to a VPC. In this post, I’ll use the VPC to create an AWS EKS cluster.

In the previous post, I looked at Pulumi to create a VPC. In this post, I’ll go over the steps to add some subnets to it.

The source code you write as a developer is important, but it is only one part of the entire application that goes into production. To deploy an app, you’ll need resources like API gateways, S3 buckets, or VPCs as well. Configuring those resources is a task you don’t want to do manually. How about building your infrastructure as code using the same language you’ve built your app in. That is what Pulumi allows you to do!

As a developer, I’ve written code and built apps, and I realized that building apps and creating a cheesecake have a lot in common. In both cases you need to have the right ingredients, you need to trust your suppliers and have transparency in your production process. I got to go to Atlanta and meet with the Docker Meetup Group there, where we got to talk about In this talk, how you can, and why you should, know what is in the app you deploy.

It was awesome to be at DevOps Days Baltimore and engage with the amazing audience there. Together with Baruch Sadogursky I got on stage to talk about how DevOps is usually viewed from a traditional perspective of a collaboration of Dev, Ops, and QA. Together with the fact that DevOps is usually driven by the change in Culture, People, and Process, the question arises how you know where you stand and where to move? As in almost any field, data and metrics give you the gauges and instruments.

It was awesome to be at DevOps Days Charlotte 2019 and speak about how you hear everything in DevOps is unicorns and rainbows, and you feel like you’re the last person on earth with “suboptimal” processes, tools and environment. Together with Baruch Sadogursky I got the chance to change the image bit. While most DevOps talks are like Instagram (everything is awesome and perfect), they hаve nothing to do with the real life.

In many talks, you hear how everything is DevOps unicorns and rainbows, and you feel like you’re the last person on earth with “suboptimal” processes, tools and environment. But no despair, DevOps talks are like Instagram, hаve nothing to do with real life. In this talk, we’ll reveal the truth.

This is the fourth and final post in the blog series on using GitHub Actions with the JFrog CLI and JFrog Artifactory. In this post we’ll look at building an app and uploading it, together with the BuildInfo, to Artifactory. If you have any thoughts on what the next series of posts should be, let me know here or on Twitter!

In 2016 TIBCO announced Project Flogo as an ultra lightweight integration engine. It is the lightest way to connect IoT devices being up to 20 to 50 times lighter than Node.js and Java® Dropwizard. Project Flogo was made available as Open Source Software because TIBCO believes there is a better way to integrate IoT devices. With it being Open Source and easily extensible, you want to make sure that the activities you build remain working after each check in on GitHub. These are a lot of words to say “How can I test my activities every time code is pushed to Git”?