Launching the Future of DevOps: GitOps 2.0
Today marks our first step towards the future. Codefresh is launching a number of new features aimed at improving the experience and speed of continuous integration and deployment with GitOps.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
A vision for GitOps 2.0
In our previous article, we explained some of the issues we see with the current generation of GitOps tools (which we call GitOps 1.0). In this article, we will talk about the solution to those issues and what we expect from GitOps 2.0 – the next generation of GitOps tooling.
Entering GitOps 2.0 with Codefresh and ArgoCD
In our previous article, we explained the vision behind GitOps 2.0 and the features we expect to be covered by GitOps 2.0 tools. In this article, we will see how the new Codefresh GitOps dashboard is the first step towards this vision and more specifically in the area of observability and traceability.
The pains of GitOps 1.0
GitOps as a practice for releasing software has several advantages, but like all other solutions before it, has also several shortcomings. It seems that the honeymoon period is now over, and we can finally talk about the issues of GitOps (and the current generation of GitOps tools) In the article we will see the following pain points of GitOps.
#Kubernetes November #Meetup
👉 Talk 1: Steering Your Helm Charts Towards Better Waters
😄 Speaker: Viswajith Venugopal, Staff Software Engineer at StackRox
My Process Used Minimal Memory, and My Docker Memory Usage Exploded
The Docker infrastructure abstracts a lot of aspects of the creation of images and running them as containers, which we usually do not know about nor interact with. One of those aspects is the handling of the filesystem inside the container. This post is a case study on how we discovered that writing large amounts of data inside a container has side effects with memory caching. Initially, we thought that we had an issue with our source code, but this was never the case.
#Kubernetes November #Meetup
👉 Talk 1: Steering Your Helm Charts Towards Better Waters 😄 Speaker: Viswajith Venugopal, Staff Software Engineer at StackRox
Managing Your Full Application Lifecycle Using #GitOps
#GitOps is nothing new. Or, to be more precise, the principles of GitOps existed long before the term was invented. But hey, that's the pattern in our industry. It is the fate of all good practices to be misunderstood, so we need to come up with new names to get people back on track. That is not to say that we are in a constant loop. Instead, I tend to think of it as a periodic reset trying to eliminate misinterpretations. GitOps is one of those resets. It fosters the practices and the ideas that existed for a while now and builds on top of them.
#GitOps: The Good, The Bad, and The Ugly
We all know what #GitOps is or what it should be. Nevertheless, not everything is full of roses and unicorns. Just as there are many benefits, we have many problems that need to be resolved both from the tooling and process perspectives. Join us in the open discussion with Viktor Farcic from #Codefresh and Adam Sandor from #ContainerSolutions
GitOps Patterns - Auto-Sync Vs. Manual Sync
The conversation usually starts with a question like “should we let ArgoCD/Flux/whatever synchronize the actual state automatically whenever the desired state changes in Git?” Truth be told, the question is usually not that elaborated, and it is more like “should I enable the auto-sync feature?” But, I wanted to save you from follow-up questions that help me better understand what that means, so I gave you a more extended and more precise version of the inquiry.