Since cycling my cluster nodes is a “fire script and wait” operation, I kicked one off today. I ended up running into an issue that required me to dig a bit into ETCD in RKE2, and could not find direct help, so this is as much my own reference as it is a guide for… Continue reading Tech Tip – Interacting with ETCD in Rancher Kubernetes Engine 2
Tag: techtip
Tech Tip – Options Pattern in ASP.NET Core
I have looked this up at least twice this year. Maybe if I write about it, it will stick with me. If it doesn’t, well, at least I can look here. Options Pattern The Options pattern is a set of interfaces that allow you to read options into classes in your ASP.NET application. This allows… Continue reading Tech Tip – Options Pattern in ASP.NET Core
Tech Tip – You should probably lock that up…
I have been running in to some odd issues with ArgoCD not updating some of my charts, despite the Git repository having an updated chart version. As it turns out, my configuration and lack of Chart.lock files seems to have been contributing to this inconsistency. My GitOps Setup I have a few repositories that I… Continue reading Tech Tip – You should probably lock that up…
Tech Tip – Not all certificates are the same
I have been trying to build a model in Azure to start modernizing one of our applications. Part of that is configuring an application gateway correctly and getting end-to-end SSL configured. As it turns out, not all certificates are good certificates, at least to Azure. Uploading the Cert I have a wildcard certificate for a… Continue reading Tech Tip – Not all certificates are the same
Tech Tip – Configuring RKE2 Nginx Ingress using a HelmChartConfig Resource
The RKE2 documentation is there, but, well, it is not quite as detailed as I have seen in other areas. This is a quick tip for customizing your Nginx Ingress controllers when using RKE2 Using Nginx Ingress in RKE2 By default, an RKE2 cluster deploys the nginx-ingress Helm chart. That’s great, except that you may… Continue reading Tech Tip – Configuring RKE2 Nginx Ingress using a HelmChartConfig Resource
Tech Tips – Moving away from k8s-at-home
Much of what I learned about Helm charting and running workloads in Kubernetes I credit to the contributors over at k8s-at-home. There expansive chart collection helped me start to jump in to Kubernetes. Last year, they announced they were deprecating their repositories. I am not surprised: the sheer volume of charts they had meant they… Continue reading Tech Tips – Moving away from k8s-at-home
Bruce Lee to the Rescue! Health Checks for .NET Worker Services
As we start to develop more containers that are being run in Kubernetes, we encounter non-http workloads. I came across a workload that represents a non-http processor for queued events. In .NET, I used the IHostedService offerings to run a simple service in a container to do this work. However, when it came time to… Continue reading Bruce Lee to the Rescue! Health Checks for .NET Worker Services
Tech Tips – Upgrading your Argo cluster tools
Moving my home lab to GitOps and ArgoCD has been, well, nearly invisible now. With the build pipelines I have in place, I’m able to work on my home projects without much thought to deploying changes to my clusters. My OCD, however, prevents me from running old versions. I really want to stay up-to-date when… Continue reading Tech Tips – Upgrading your Argo cluster tools
Nginx Reverse proxy: A slash makes all the difference.
I have been doing some work to build up some standard processes for Kubernetes. ArgoCD has become a big part of that, as it allows us to declaratively manage the state of our clusters. After recovering from a small blow-up in the home lab (post coming), I wanted to migrate my cluster tools to utilize… Continue reading Nginx Reverse proxy: A slash makes all the difference.
Tech Tip – Azure DevOps Pipelines Newline handling
Just a quick note: It would seem that somewhere between Friday, April 29, 2022 and Monday, May 2, 2022, Azure DevOps pipelines changed their handling of newlines in YAML literal blocks. The change caused our pipelines to stop executing with the following error: What caused it? Multi-line, inline block definitions.