Migrating repositories with LFS can be tricky. This is especially true when the repository is configured to use an LFS endpoint that is separate from the Git repository. Learn how to safely migrate repositories that are using .lfsconfig to manage the storage location.

Like any other software lifecycle, infrastructure-as-code solutions can mature over time. But how do we know where we are in our maturity and the steps to take to improve? This post introduces a maturity model that you can use for infrastructure-as-code. It also explores how you can use composition and reusability to improve your solutions and make them more testable.

Historically, there’s been no way to really apply resource requests or limits at the pod level in Kubernetes. Instead, we are forced to apply these configurations at the container level. Thankfully, there is a new feature in Kubernetes that promises to change that.

Since it’s the gift-giving season, it seems like the perfect time to wrap up the posts about how to distribute packages. More specifically, how to distribute dependencies and settings with NuGet packages.

Kubernetes native sidecars can create more reliable deployments. In this post, we’ll explore how to improve the Docker-in-Docker implementation in GitHub Actions Runner Controller (ARC) using native sidecars.

Kubernetes is constantly growing and evolving. One of those features is getting ready to become generally available soon: native sidecars. Learn what they are, the problems they solve, and how to use them.

Unlocking the power of GitOps means learning to use Git as the source of truth for deployments. Key to that is understanding the three models used for defining your GitOps practices.

Packages are code, too! Like any other code solution, it’s important to be able to test your work. In this post, you’ll learn how to test a custom .NET package that adds ZIP support to the build process.

In my last post, I showed you how to use MSBuild to automatically create a ZIP package for deployment in .NET. Now, I’ll show you how to automate distributing those changes to developers using a NuGet package.

The process of compiling a .NET project and creating a ZIP file for deployment is often more complicated than it needs to be. Most CI/CD systems use a series of commands and external dependencies to build and package the project. This post shows how to use built-in functionality to simplify the process to a single call to dotnet publish.