<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://www.jfe.cloud/</id><title>JFE's Tech Blog</title><subtitle>A blog of an IT Pro, sharing knowledge and experience in the field of IT. This blog covers a wide range of topics, including programming, cloud computing, and IT security. The goal is to provide valuable insights and practical tips for IT professionals and enthusiasts alike.</subtitle> <updated>2025-04-12T17:00:29+02:00</updated> <author> <name>Jonas Feller</name> <uri>https://www.jfe.cloud/</uri> </author><link rel="self" type="application/atom+xml" href="https://www.jfe.cloud/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://www.jfe.cloud/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2025 Jonas Feller </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>The case of the missing AKS route table assignment</title><link href="https://www.jfe.cloud/posts/the-case-of-the-missing-aks-route-table-assignment/" rel="alternate" type="text/html" title="The case of the missing AKS route table assignment" /><published>2020-02-18T00:00:00+01:00</published> <updated>2025-04-12T15:53:28+02:00</updated> <id>https://www.jfe.cloud/posts/the-case-of-the-missing-aks-route-table-assignment/</id> <content type="text/html" src="https://www.jfe.cloud/posts/the-case-of-the-missing-aks-route-table-assignment/" /> <author> <name>Jonas Feller</name> </author> <category term="Azure" /> <category term="AKS" /> <summary>TL;DR If you use the advanced networking (Azure CNI) option then this post is not relevant for you as in that case no route table and UDR is involved. By default an AKS cluster is created with the ‘kubenet’ aka. basic networking option which depends highly on Azure ‘User Defined Routing’ (UDR). Therefore during the deployment of the AKS cluster a route table Azure resource is automaticall...</summary> </entry> <entry><title>Control pipeline artifacts upload with the .artifactignore file in Azure DevOps Pipelines</title><link href="https://www.jfe.cloud/posts/control-pipeline-artifacts-with-artifactignore-file/" rel="alternate" type="text/html" title="Control pipeline artifacts upload with the .artifactignore file in Azure DevOps Pipelines" /><published>2019-07-21T00:00:00+02:00</published> <updated>2019-07-21T00:00:00+02:00</updated> <id>https://www.jfe.cloud/posts/control-pipeline-artifacts-with-artifactignore-file/</id> <content type="text/html" src="https://www.jfe.cloud/posts/control-pipeline-artifacts-with-artifactignore-file/" /> <author> <name>Jonas Feller</name> </author> <summary>Build vs. Pipeline Artifacts With the classic build and release pipelines, which are still know form the time back where Azure DevOps was named VSTS (Visual Studio Team Services) and which were created then with the graphical editor, the build pipeline normally published at the end an artifacts with the ‘Publish Build Artifacts’ task. This was back then actually also the only way to publish bu...</summary> </entry> <entry><title>Using the SSH server in Windows Server 2019</title><link href="https://www.jfe.cloud/posts/using-the-ssh-server-in-windows-server-2019/" rel="alternate" type="text/html" title="Using the SSH server in Windows Server 2019" /><published>2019-02-14T00:00:00+01:00</published> <updated>2019-02-14T00:00:00+01:00</updated> <id>https://www.jfe.cloud/posts/using-the-ssh-server-in-windows-server-2019/</id> <content type="text/html" src="https://www.jfe.cloud/posts/using-the-ssh-server-in-windows-server-2019/" /> <author> <name>Jonas Feller</name> </author> <summary>Yes, your are reading it right. Windows Server has now also a built in SSH Server for remote access. And it is not just any SSH server it is an official Win32 port of the popular OpenSSH server, maintained and official supported by Microsoft. The same OpenSSH you already may know form your favorite Linux distribution or from macOS. So an other nice example how Microsoft has changed in the last ...</summary> </entry> <entry><title>Export and import Azure Blueprints definitions</title><link href="https://www.jfe.cloud/posts/export-import-azure-blueprints/" rel="alternate" type="text/html" title="Export and import Azure Blueprints definitions" /><published>2018-11-14T00:00:00+01:00</published> <updated>2018-11-14T00:00:00+01:00</updated> <id>https://www.jfe.cloud/posts/export-import-azure-blueprints/</id> <content type="text/html" src="https://www.jfe.cloud/posts/export-import-azure-blueprints/" /> <author> <name>Jonas Feller</name> </author> <summary>Azure Blueprints are relatively new and currently in public preview. With Azure Blueprint you can deploy and update a set of different Azure resources and configurations in a repeatable way and can be really useful to define and apply your standards and foundations to Azure subscriptions. For a general overview what Azure Blueprints are and how they can be used I would recommend to read the ‘Az...</summary> </entry> <entry><title>Useful PowerShell snippets for Storage Spaces Direct (S2D) operations</title><link href="https://www.jfe.cloud/posts/useful-powershell-snippets-for-storage-spaces-direct-s2d-operations/" rel="alternate" type="text/html" title="Useful PowerShell snippets for Storage Spaces Direct (S2D) operations" /><published>2018-05-30T00:00:00+02:00</published> <updated>2018-05-30T00:00:00+02:00</updated> <id>https://www.jfe.cloud/posts/useful-powershell-snippets-for-storage-spaces-direct-s2d-operations/</id> <content type="text/html" src="https://www.jfe.cloud/posts/useful-powershell-snippets-for-storage-spaces-direct-s2d-operations/" /> <author> <name>Jonas Feller</name> </author> <summary>This is a very quirk post to just share some simple PowerShell snippets I have created or found elsewhere which I find very handy when it comes to troubleshooting, setup or operating Storage Spaces Direct (S2D). 1. Get the count of physical disk in each node When S2D is enabled in a cluster Get-Physicaldisk returns the physical disk from all cluster nodes. But when you want the disk count of ...</summary> </entry> </feed>
