<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Vmss on Ash Tewari</title><link>https://www.tewari.info/tag/vmss/</link><description>Recent content in Vmss on Ash Tewari</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 28 Mar 2021 03:33:11 +0000</lastBuildDate><atom:link href="https://www.tewari.info/tag/vmss/feed.xml" rel="self" type="application/rss+xml"/><item><title>AKS - Adding SSH Keys to VMSS Nodes</title><link>https://www.tewari.info/2021/03/27/aks-adding-ssh-keys-to-vmss-nodes/</link><pubDate>Sun, 28 Mar 2021 03:33:11 +0000</pubDate><guid isPermaLink="false">https://www.tewari.info/?p=1274</guid><description>&lt;p&gt;You can connect to Azure Kubernetes Service (AKS) nodes using ssh. It is documented here: &lt;a href="https://docs.microsoft.com/en-us/azure/aks/ssh"&gt;Connect with SSH to Azure Kubernetes Service (AKS) cluster nodes for maintenance or troubleshooting&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I needed to access nodes on the System node pool for collecting some logs recently, but the process documented above was not working for me. It turns out that there were two different issues, both related to adding your SSH keys to the nodes in a virtual machine scale set (VMSS).&lt;/p&gt;</description></item></channel></rss>