<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
	<channel>
		<title>Visual Studio Geeks</title>
		<atom:link href="https://www.visualstudiogeeks.com/feed.xml" rel="self" type="application/rss+xml" />
		<description>Great posts on DevOps, Azure, GitHub, Azure DevOps (VSTS) and Visual Studio</description>		
		<language>en-US</language>
		<link>https://www.visualstudiogeeks.com</link>
		<pubDate>Sun, 10 Mar 2024 15:51:04 +0000</pubDate>
    	<lastBuildDate>Sun, 10 Mar 2024 15:51:04 +0000</lastBuildDate>
    	<generator>Jekyll v4.3.3</generator>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
		
			
			<item>
				<title>Exploring GitHub Advanced Security for Azure DevOps</title>
				<link>https://www.visualstudiogeeks.com/devops/github/exploring-github-advanced-security-for-ado</link>
				<pubDate>Sat, 17 Feb 2024 00:00:00 +0000</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;It has been a few months since GitHub Advanced Security (GHAS) has been made generally available for Azure DevOps. During this time, I’ve engaged with numerous customers eager to implement GHAS within their Azure subscriptions. In this post, I wanted to show you a quick way to set up GHAS within Azure DevOps and explore the features available.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/devops/github/exploring-github-advanced-security-for-ado</guid>
			</item>
		
			
			<item>
				<title>Use a single repository for multiple wikis in Azure DevOps</title>
				<link>https://www.visualstudiogeeks.com/azure%20devops/using-single-azdo-repo-for-multiple-wikis</link>
				<pubDate>Thu, 07 Dec 2023 00:00:00 +0000</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;This is a quick post to share how you can use a single Azure DevOps repository for multiple wikis in Azure DevOps. This approach will help you avoid creating multiple repositories for each wiki and manage them in a single repository.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/azure%20devops/using-single-azdo-repo-for-multiple-wikis</guid>
			</item>
		
			
			<item>
				<title>Creating KEDA Scalar in Azure Container Apps using Azure Portal</title>
				<link>https://www.visualstudiogeeks.com/devops/creating-keda-scalar-in-aca-using-azure-portal</link>
				<pubDate>Wed, 22 Nov 2023 00:00:00 +0000</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;In this post, I would like to show you how we added custom scaling with KEDA using the Azure Portal — Thanks to the KEDA scaler, we have a dynamic scaling pool, which automatically scales when there are more jobs in the queue and scales back down when demand reduces.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/devops/creating-keda-scalar-in-aca-using-azure-portal</guid>
			</item>
		
			
			<item>
				<title>Installing Docker without Docker Desktop on WSL2</title>
				<link>https://www.visualstudiogeeks.com/productivity/installing-docker-without-docker-desktop-on-wsl2</link>
				<pubDate>Wed, 04 Oct 2023 00:00:00 +0100</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;I have been using Docker on WSL2 without Docker Desktop for a while now and recently I had to rebuild my Ubuntu distro. I had to go through installing the Docker Engine once again following a series of steps, so thought I would document it so that I can use it again as a reference.&lt;/p&gt;

&lt;p&gt;This post is just that and I hope others will find it useful too.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/productivity/installing-docker-without-docker-desktop-on-wsl2</guid>
			</item>
		
			
			<item>
				<title>Trigger a Netlify build every day using GitHub Actions</title>
				<link>https://www.visualstudiogeeks.com/github/netlify/trigger-netlify-build-everyday-using-github</link>
				<pubDate>Sun, 20 Feb 2022 00:00:00 +0000</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;I host this blog on Netlify. Often, I end up writing few blog posts on the same day, but not necessarily want all of them published together. Jekyll allows to add future date to the posts, and those posts will not get published until the date set. This lets me write blog posts on the same day, but publish them later based on the date set for the post.&lt;/p&gt;

&lt;p&gt;However, this means that when you build the site (locally or on Netlify), posts with future dates will be skipped from the generated site. You will need to run build again on the blog post date to publish the blog posts. One way is to schedule a build on Netlify so that blog posts with future date can be included in the site. Curious how to do this?&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/github/netlify/trigger-netlify-build-everyday-using-github</guid>
			</item>
		
			
			<item>
				<title>Policy enforced deployments for your Kubernetes resources</title>
				<link>https://www.visualstudiogeeks.com/azure/kubernetes/devops/policy-enforcement-for-k8s</link>
				<pubDate>Sun, 13 Feb 2022 00:00:00 +0000</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;As your team starts to deploy resources to Kubernetes regularly, it becomes necessary for you as a cluster administrator to maintain  good standards and consistency of the Kubernetes resources. Be it, ensuring all the resources have set of labels, or ensuring you only pull images from your enterprise container registry. &lt;a href=&quot;https://github.com/open-policy-agent/gatekeeper&quot;&gt;Gatekeeper&lt;/a&gt; is a well known policy enforcement tool using &lt;a href=&quot;https://www.openpolicyagent.org&quot;&gt;Open Policy Agent (OPA)&lt;/a&gt; - which is a opensource, Cloud Native Computing Foundation (CNCF) project.&lt;/p&gt;

&lt;p&gt;But did you know you can validate policies on your Kubernetes manifests before you deploy them on to the cluster? In this post, we will see how we can govern our deployments using Conftest and OPA policy agent.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/azure/kubernetes/devops/policy-enforcement-for-k8s</guid>
			</item>
		
			
			<item>
				<title>Keep your workflow actions up to date using GitHub Dependabot</title>
				<link>https://www.visualstudiogeeks.com/github/ensure-your-actions-are-up-to-date</link>
				<pubDate>Fri, 28 Jan 2022 00:00:00 +0000</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;GitHub Actions is great in automating your workflows. However, as you start using various actions from GitHub Marketplace in your workflow, it will soon become necessary for you to keep the actions up-to-date. Actions might contain security fixes, bug fixes etc and manually keeping track of updates or updating them when a newer version is available is a lot of hassle. This is where we can use Depndabot, which can help by automatically raising PR’s whenever there is a newer version of action is available used in the workflow. In this post, we will see quick way to keep the actions up-to-date using GitHub Dependabot.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/github/ensure-your-actions-are-up-to-date</guid>
			</item>
		
			
			<item>
				<title>Setting up Azure Cosmos DB Emulator on Synology NAS</title>
				<link>https://www.visualstudiogeeks.com/azure/cosmos/setting-up-cosmos-db-emulator-on-synology</link>
				<pubDate>Tue, 27 Jul 2021 00:00:00 +0100</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;Cosmos DB Emulator is great for developing against Azure Cosmos DB in your local environment. If you want to run the emulator on Mac/Linux though, the emulator is now in preview mode at the time of writing this and uses Docker to make it available.&lt;/p&gt;

&lt;p&gt;Recently I wanted to setup Cosmos DB Emulator on Mac, but I did not want to set it up such that I keep it running always on my Mac. Instead, I decided to use my Synology NAS to host the emulator directly on my NAS as it is built on Linux and also because it allows the emulator running and available for me all the time.&lt;/p&gt;

&lt;p&gt;In this post we will see how to set it up on Synology NAS.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/azure/cosmos/setting-up-cosmos-db-emulator-on-synology</guid>
			</item>
		
			
			<item>
				<title>How to publish Helm 3 charts to GitHub Container Registry using GitHub Actions</title>
				<link>https://www.visualstudiogeeks.com/github/publish-helm-3-charts-to-gcr</link>
				<pubDate>Sat, 10 Apr 2021 00:00:00 +0100</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;I have already written how to publish Helm chart to ACR using &lt;a href=&quot;/devops/helm/deploying-helm-chart-with-azdo&quot;&gt;Azure DevOps&lt;/a&gt; and &lt;a href=&quot;/helm/devops/publish-helm-charts-to-acr-using-github-actions&quot;&gt;GitHub actions&lt;/a&gt;. But did you know that you can also publish Helm3 charts (or any OCI compliant package) to &lt;a href=&quot;https://github.blog/2020-09-01-introducing-github-container-registry/&quot;&gt;GitHub Container Registry(GCR)&lt;/a&gt;? In this post we will see how to do that.&lt;/p&gt;
]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/github/publish-helm-3-charts-to-gcr</guid>
			</item>
		
			
			<item>
				<title>Publish Helm 3 charts to Azure Container Registry (ACR) using GitHub Actions</title>
				<link>https://www.visualstudiogeeks.com/helm/devops/publish-helm-charts-to-acr-using-github-actions</link>
				<pubDate>Thu, 01 Apr 2021 01:00:00 +0100</pubDate>
				
					<dc:creator><![CDATA[Utkarsh Shigihalli]]></dc:creator>
				        
				
					<description><![CDATA[&lt;p&gt;In my &lt;a href=&quot;/devops/helm/deploying-helm-chart-with-azdo&quot;&gt;previous&lt;/a&gt; post, we briefly covered how to publish a Helm chart to ACR using Azure DevOps. In this post we will use GitHub actions to build and publish Helm chart to ACR using GitHub Actions. We will also take a sneak peak how GitHub environments work.&lt;/p&gt;

]]></description>
				
				<guid isPermaLink="true">https://www.visualstudiogeeks.com/helm/devops/publish-helm-charts-to-acr-using-github-actions</guid>
			</item>
		
	</channel>
</rss>
