“The King is dead, long live the King.” It might be my french roots speaking, but it seems that actual use cases are replacing King Edge, and it might be for the best. Warning; do not read this blog if you’re particularly sensitive about edge computing (and if you don’t know what this is about, read the “What’s the deal with edge computing?” blog first).
Ninjas are known for their stealth and agility, skills that take much practice and study to master. They are never satisfied with their current abilities and always seek to improve. Those noble aspirations are not limited to secret warriors. In the current climate, IT leaders are also busy adding new capabilities to their skillset. In my IT Experience Podcast, I regularly sit-down with IT pros who have valuable advice for their peers.
As you may know, InfluxDB is available in multiple forms, including InfluxDB Open Source and InfluxDB Cloud. Customers will sometimes ask us, “If I’m using InfluxDB Cloud, is there any reason I should also consider using InfluxDB open source?” It’s a fair question.
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.
I’ve been primarily a Javascript developer for a long time now, it’s been my go-to language for the better part of a decade now, I even wrote a post on how to implement observability in a traditional Node.js application. Now, on top of hacking around in JS, I also love building things for AWS Lambda which is AWS’s option for Functions-as-a-Service.
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.
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.
After months of hard work with our team of 6. We're glad to announce that our deployment engine is now open-source. Now it's time and possible to contribute. Qovery engine is still under development, but more than 600 developers and dozens of successful companies use our Engine for 11 months through Qovery.
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.
In todays IP-centric world, it’s becoming increasingly complex to support network-intensive adaptations like cloud adoption and bring your own device (BYOD) polices. As an IT admin, you’re responsible for scanning and tracking your IP resources to ensure that network devices and end users can be allocated unique IP addresses to access your network.
