Lessons learned, tips and documentation provided by the Humanitec team.
GitOps takes familiar tools such as Git and Continuous Delivery pipelines to automate infrastructure. The GitOps approach is vendor-neutral, provides a clear history of changes, and allows you to reproduce or roll back deployments. Yet, we can't ignore the problems with this approach: Proliferation of repositories, no help for secrets management, or simultaneous file writes. Let's explore.
There is a fundamental design flaw with Helm, leading to dramatic long-term consequences and you have to solve this now.
A major bug urgently needs fixing in Production, but QA is impossible because Staging is ahead of Prod. This blog post will detail how to clone your Production environment to allow immediate testing before hot-fixing Production.
Your Kubernetes configuration represents environments that are a fundamental part of your application, unyet we generally treat them as less important from our application code. In this post we look at best practices for managing changes to configuration, and how to treat it the way it deserves.
We are proud to announce that Humanitec has become an official technology partner of CircleCI and their Orb program. CircleCI users can now seamlessly integrate their CircleCI build pipeline with Humanitec’s workflows. Using Humanitec’s Orb, they can build and push new images to Humanitec and improve the maintenance of their Kubernetes-ready applications after every CircleCI build.
Interest in DevOps adoption has increased. Most teams are either running automated deployments or are hoping to run them in the future as they look to improve their workflow and workplace practices. Being able to deploy your environments automatically is an excellent opportunity to optimize developer productivity.
We are very excited to make the Humanitec API available as a public Beta today! Our API provides the same functionality teams have enjoyed through our UI - but now allows for more opportunities for automation and integration.
In this article, we look at ephemeral testing environments, small, discrete, and short-lived testing environments that reflect only the changes you are interested in testing.
Continuous delivery helps software development teams get their code changes from development to testing, and into the hands of users more quickly. In this post, Chris Ward looks at the benefits and best practices for implementing this practice into your teams.
Lead time is a critical metric to enable a company to improve its speed of deployment. We take a deep dive into how lead time differs across organizations, how it can be improved and where it fits into the greater context of improving business outcomes.
Despite sounding similar, continuous integration, delivery, and deployment are subtly different from each other. While they have overlap, they are applicable and useful at different stages of the development process. In this post, we look at what the different terms mean, what benefits they bring to you and your team, and what you need to get started implementing the practice.