DevOps

This article is a part of the GitLab for .NET developer series. In the previous article I described how to use my AutoDevOps library to replace the GitLab AutoDevOps deployment entirely with a Pulumi stack, so you can deploy your workloads and other resources without using Helm, or even deploy other type of resources outside of Kubernetes in the same stack. Automation API A couple of years ago, Pulumi announced their Automation API. [Read More]

This article is a part of the GitLab for .NET developer series. In the previous article I described the work I’ve done to move more parts of the GitLab AutoDevOps deployment to C# code that uses Pulumi. This article explains how the library I created based on all that work, can be used in a real-life scenario. Using Ubiquitous.AutoDevOps The Ubiquitous.AutoDevOps NuGet package is a set of tools that allow to replace the default GitLab AutoDevOps deployment using bash and Helm, with a single deployment project using Pulumi. [Read More]

This article is a part of the GitLab for .NET developer series. It’s been a while since I published my last article about replacing Helm charts in the GitLab CI/CD pipeline with Pulumi deployment programs. Between August last year and now I’ve tried quite a lot of different things to improve the flow, so I am now ready to share my experience. What didn’t feel right First, let me explain why I thought it’s not the end of it, and decided to continue my experiments. [Read More]

This article is a part of the GitLab for .NET developer series. We actively use the modified GitLab AutoDevOps pipeline that supports .NET applications better than the original one. I described our approach in the previous article. GitLab AutoDevOps feature uses Helm and therefore I had to create my own Helm chart with some amendments. However, the cart is still very rigid. Rigidity the common issue with Helm charts and trying to develop a chart to cover a lot of different deviations from the default is a road to hell. [Read More]

This article is a part of the GitLab for .NET developers series. GitLab is the awesome tool that I used in different organisations for years. It is, however, often overlooked in the .NET space. One of the reasons for this is that GtLab was always oriented to more dynamic stacks and .NET used to be quite rigid and enterprise-oriented space. When it comes to continuous delivery, I believe that GitLab is one of the best, if not the best integrated tool on the market today. [Read More]

Update: GitLab currently has a choice of cloud-native Helm charts, which might be more actual than using this recipe. Check this page to find out more. I would like to share my experience to create a small Kubernetes cluster on Azure Container Service (AKS Preview) and deploy GitLab CE there using the Helm chart. Creating a cluster in AKS should be an easy task but sometimes things don’t go at they suppose to. [Read More]