Ryan Cook

Recent Posts

Introduction to Tekton and Argo CD for multicluster development

Introduction to Tekton and Argo CD for multicluster development

Over the last two years, my coworkers and I have worked on developing a multicluster project for Kubernetes and Red Hat OpenShift. We needed a way to efficiently deploy applications, oversee access and authorization, and manage application placement across clusters. This need led us to develop with Argo CD and GitOps.

Recently, I switched to another team that also focuses on multicluster development. During my interviews, I promised to help create a catalog of our projects and develop a process to deploy them rapidly. Together, the catalog and process would allow the team to just work on things, rather than trying to figure out how to get them operational. However, I quickly hit a wall. With Argo CD, I couldn’t control when and in what order cluster objects were deployed onto new or existing clusters. Eventually, I discovered Tekton, a powerful addition to my development toolset.

In this article, I briefly describe my process for developing the catalog and process tool. I’ll introduce the components involved, explain a little about how Tekton Pipelines works, and leave you with a tool that you can share with your organization and teams.

Continue reading “Introduction to Tekton and Argo CD for multicluster development”

Share

Mixing developers and systems administrators for speed and value

https://openclipart.org/detail/188792/conversation-by-ousia-188792In many organizations development teams are split up from systems administrators.  Both teams focus mainly on their roles and responsibilities, but this can lead to problems.  Tensions between the groups can hinder your organization’s efforts in getting the best product to the consumers in the shortest amount of time. Below are quotes which are commonly come up between developers and systems administrators.

  • “Why doesn’t the development team have to be on call? It’s their code that breaks the system.”
  • “Why does the sysadmin get to dictate what tools/languages I can use to solve the problem?”
  • “Add more hardware to the server”
  • “Stop using so many resources on the system!”

You begin to easily see how this relationship is strained and broken, but does it have to be? Let’s talk about some more of the common stereotypes and discuss the ways to move past them.

Continue reading “Mixing developers and systems administrators for speed and value”

Share
How Team Inception CI/CDs

How Team Inception CI/CDs

Our infrastructure and how we continuously integrate and deliver (CI/CD) our code changes with each piece of work we finish. We fully expect that it will change even more as we bring up A|B functionality & enhance our testing process. However, we thought it would be fun to give a closer look into the team’s pipeline from checking out code to integration testing.

CI/CD Team Inception

Continue reading “How Team Inception CI/CDs”

Share

How Red Hat’s Inception DevOps team utilized Docker for the Release Engine

As we have discussed in the past, Team Inception has been working on a release engine to automate RPM code deployments within Red Hat IT. On July 8 we passed a significant milestone by successfully using Release Engine in our QA environment.  This was an incredible achievement which included a number of feature requests, defect fixes, and collaboration between multiple teams to produce an open source application that will address growing needs internally in Red Hat ITWe decided that since we are attempting to make waves internally we should also use a product that is currently making waves throughout the industry: so we chose Docker.

Continue reading “How Red Hat’s Inception DevOps team utilized Docker for the Release Engine”

Share