You can use CircleCI’s cloud resources to run your CI/CD jobs, but there may be times you want to run them on your infrastructure. If your team imposes privileged access and control requirements, a self-hosted infrastructure might be best for running your jobs. CircleCI’s self-hosted runners lets you do exactly that. It is easy to get started and start using self-hosted runners.

We’ve all seen the news about tech layoffs. If you’re an engineering manager, are you having to squeeze more out of existing teams, because adding staff anytime soon is unlikely? Maybe you’re tempted to micromanage your developers, thinking that if you know every aspect of their work, it’ll boost productivity. But, that approach doesn’t feel right, and you know your devs would hate you for it. What’s an engineering manager to do?

Planning to deploy Argo CD and support a lot of Kubernetes clusters? In this article, we’ll cover the different deployment strategies and architectures used along with their pros and cons. A Comprehensive Overview of Argo CD / GitOps Architectures – 2023

Argo CD is a declarative continuous delivery tool for Kubernetes developed by the Cloud Native Computing Foundation (CNCF). Argo CD automates your application deployment by continuously monitoring the live state of your containers and comparing it against the desired state in your Kubernetes manifest files, then pulling changes into your Kubernetes clusters as needed.

Containers are a useful tool for deploying applications because they allow for the packaging of an application’s code, libraries, and dependencies into a single, isolated unit. This makes it easy to deploy and run the application on any computer or server that has the necessary container software installed.