Why Is Kubernetes Ideal for CI/CD and Reinforcing DevOps Goals?

In the current scenario, when companies are struggling with setting up their CI/CD pipelines for cloud-based applications, Kubernetes, a powerful open-source platform for automating the deployment, scaling, and management of application containers across hosts, has reinforced DevOps goals and proven to be the ideal solution to CI/CD. It not only improves traditional DevOps processes, including speed, efficiency, and resiliency, but also solves newer problems that comes with containers and micro services-based application architectures. In a quick interview at the DevOps World | Jenkins World 2018 event with DevOps.com Managing Editor Charlene O’Hanlon, Mike Maheu, VP – Engineering and Strategy, Go2Group, highlighted the increasing demand and conversations around Kubernetes and containerization, and the requirement of “speedy delivery with precision.” The most common question companies ask today is “how can we configure our applications so that we can do CI/CD with containers?” Mike also points out the challenges many organizations face in adopting DevOps. Here’s an excerpt of the interview. Charlene: Tell us a little about Go2Group and its services Mike: Go2Group has been in business for 13 years. We started out in source control management. We partnered with Atlassian 11 years ago. We basically help medium and small companies to develop software better through best practices and tooling. We strategically partner with companies like CloudBees and others so that we can become experts around tooling. We help companies improve not only with development but also agile — the entire requirements to delivery pipeline. That’s why we are here talking about DevOps. Charlene: Do you get into the trenches with these companies? Mike: We do get into the trenches. We do analysis and assessment to see what kind of services they require; a lot of large companies are fragmented with their tooling. So, we come up with a strategy. Agile has been around for a while and a lot of companies are good at it. But the problem today is that they can’t really deliver code quickly. They can iterate and sprint but can’t deliver code as fast as they iterate and sprint. So we are tightly coupling the DevOps aspect — the delivery part of it — with the rest of the software lifecycle.
The most common question companies ask today is “how can we configure our applications so that we can do CI/CD with containers?” — Mike Maheu, VP – Engineering and Strategy, Go2Group
Charlene: What are the biggest impediments for companies in moving code quickly? Mike: It goes top down. A lot of times there is not a lot of buy-in from the corporate perspective. A lot of the tools come from the bottom and end up with fragmentation. So, there should be a process that couples the actual tooling and what they (companies) are trying to do. Larger companies have multiple software, products, and a lot of different teams. The higher level wants to see across the landscape and they want to make sure that they are able to deliver the changes to their applications. The voices are raised up to the top. And they are struggling with delivering software — when we look at the old school ways of “here’s our application, please deploy in the same environment (sic).” These days I am talking a lot about newer technologies like containerization with Docker, Kubernetes, Jenkins Core, and tying things to the cloud. A lot of companies are also wanting to move their on-premise tooling to cloud tooling. Charlene: Are a majority of these applications and development work being moved to the cloud or are they between cloud and on-premises? Mike: Not long ago, larger companies — government and financial — were scared of the cloud. The first step was when some of them got onto Git for their source control management and Atlassian has Bitbucket (sic). People started hosting their code outside their fortress. The first thing that large companies agree to put on their cloud are their Dev tools. Its low risk – the best bet to get speed of delivery when we talk about containerization and the power of the cloud to deliver at scale. It’s a powerful thing! Watch the full interview https://www.go2group.com/resources/videos/ For more information, write to us at marcom@go2group.com

Go2Group’s Solutions Architect Shares Top-notch Ubuntu Tips in Latest Book

“I’ve always been a big fan of the Ubuntu platform, having used it since the very first release. My goal is to pass along my extensive knowledge of Ubuntu to others.” Jeremy (Jay) LaCroix, Solutions Architect, Go2Group With the newest Ubuntu Server 18.04 having taken data centres by storm and becoming popular with features such as new default desktop GNOME 3.28, better boot speed, new “minimal installation” option, new default applications, Linux Kernel 4.15 and others, it is more than essential to understand how to master Ubuntu. Read more

Good Habits of a Software Engineer

I recently read a post on Quora about habits that can make you a better software engineer. Here are three good habits that every software engineer should adopt: Read more

Docker Swarm on AWS

Docker Swarm is Docker’s native clustering solution. It turns a group of Docker Engines into a single, virtual Docker engine using an API proxy system.  Here are some of the benefits of using Docker Swarm and advice on deploying a Docker Swarm into AWS. Read more

Webinar recap: Highlights of testing expert webinar, “Test Automation Trends for 2016 and Beyond”


In a previous blog post, I highlighted the expertise of test automation guru Joe Colantonio, famous for his popular weekly podcast, TestTalks. In January 2016, Joe delivered a webinar entitled, “Test Automation Trends for 2016 and Beyond” for testing automation vendor, SauceLabs. In the webinar, he discussed the skills, best practices, and frameworks required to stay employable in today’s constantly changing development/testing world. Read more

Distorting your project’s progression by intentionally downplaying defects: developer already fixing it (part 4 of 4)

Welcome to the last part of the “downplaying defects” series, and thanks for reading all the way through.  In this month’s installment we’ll discuss a scenario wherein QA finds a defect already discovered by the developer. The defect is being fixed, but no defect report has been submitted.

Read more

Distorting your project’s progression by intentionally downplaying defects: not an actual requirement (part 3 of 4)

In my previous installment in this series, I discussed developers rejecting defects for the arbitrary rationale of a QA tester questioning the bug’s legitimacy In this installment, we’ll talk about a scenario in which the developer or another team member rejects a defect, but for a different motivation: it’s not classified as an actual requirement. We’ll see, however, that with the proper skill and knowledge leveraged by the QA tester, and with proper engagement with the author or owner of the requirements, these situations can be turned into an opportunity for the requirement to be corrected, or more clearly expressed. Read more

Collection of software QA “Go2” testing resources

Many of us who have been in the testing field for a while have gathered a list of resources that we find ourselves going back to over and over again for quick information about industry products, or help with a question or a problem. Read more

Git performance testing: Real-world results – More on test profiles (part 4 of 4)

To wrap up our blog series on Git performance testing, here are a few charts that show the typical load we placed on the servers.

Let’s start with repository size. It’s well known that Git doesn’t handle large repositories well, so we kept most repositories around a typical size of under 200 MB. Read more

Git performance testing: Real-world results – Hardware characteristics (part 3 of 4)

In terms of server sizing, what should you watch out for?

Read more