<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Create an Azure Container Registry and allow AKS access	</title>
	<atom:link href="https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/feed/" rel="self" type="application/rss+xml" />
	<link>https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=create-an-azure-container-registry-and-allow-aks-access</link>
	<description>A blog about Azure Kubernetes Service (AKS) and more...</description>
	<lastBuildDate>Sun, 05 May 2019 07:38:14 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>
		By: Pixel Robots.		</title>
		<link>https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/#comment-356</link>

		<dc:creator><![CDATA[Pixel Robots.]]></dc:creator>
		<pubDate>Sun, 05 May 2019 07:38:14 +0000</pubDate>
		<guid isPermaLink="false">https://pixelrobots.co.uk/?p=32690#comment-356</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/#comment-355&quot;&gt;Edward Pius&lt;/a&gt;.

Hello, As long as your subscriptions are under the same tenant, then yes create a Service Principal that is scopes to all your subscriptions.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/#comment-355">Edward Pius</a>.</p>
<p>Hello, As long as your subscriptions are under the same tenant, then yes create a Service Principal that is scopes to all your subscriptions.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Edward Pius		</title>
		<link>https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/#comment-355</link>

		<dc:creator><![CDATA[Edward Pius]]></dc:creator>
		<pubDate>Sun, 05 May 2019 03:56:29 +0000</pubDate>
		<guid isPermaLink="false">https://pixelrobots.co.uk/?p=32690#comment-355</guid>

					<description><![CDATA[Hello Richard,

I have configured an ACR in a different subscription. My intention is to create one K8S cluster per subscription. We want to have different subscriptions per environment (dev/uat/stage/prod). The ACR will live on a &quot;shared&quot; subscription. So, in this case, I am guessing that I have to create a service principal which has access to all the required subscriptions?

Before reading this article, I was creating a K8S secret with the ACR information to access the images per subscription/namespace. If this can be done using across multiple subscriptions, that would be really nice.

Thanks,

Edward]]></description>
			<content:encoded><![CDATA[<p>Hello Richard,</p>
<p>I have configured an ACR in a different subscription. My intention is to create one K8S cluster per subscription. We want to have different subscriptions per environment (dev/uat/stage/prod). The ACR will live on a &#8220;shared&#8221; subscription. So, in this case, I am guessing that I have to create a service principal which has access to all the required subscriptions?</p>
<p>Before reading this article, I was creating a K8S secret with the ACR information to access the images per subscription/namespace. If this can be done using across multiple subscriptions, that would be really nice.</p>
<p>Thanks,</p>
<p>Edward</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Edward Pius		</title>
		<link>https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/#comment-354</link>

		<dc:creator><![CDATA[Edward Pius]]></dc:creator>
		<pubDate>Sun, 05 May 2019 03:52:46 +0000</pubDate>
		<guid isPermaLink="false">https://pixelrobots.co.uk/?p=32690#comment-354</guid>

					<description><![CDATA[Hello Richard,

I have configured an ACR in a different subscription. My intention is to create one K8S cluster per subscription. We want to have different subscriptions per environment (dev/uat/stage/prod). The ACR will live on a &quot;shared&quot; subscription. So, in this case, I am guessing that I have to create a service principal which has access to all the required subscriptions?

Before reading this article, I was creating a K8S secret with the ACR information to access the images per subscription/namespace. If this can be done using across multiple subscriptions, that would be really nice.

Thanks,

Edward]]></description>
			<content:encoded><![CDATA[<p>Hello Richard,</p>
<p>I have configured an ACR in a different subscription. My intention is to create one K8S cluster per subscription. We want to have different subscriptions per environment (dev/uat/stage/prod). The ACR will live on a &#8220;shared&#8221; subscription. So, in this case, I am guessing that I have to create a service principal which has access to all the required subscriptions?</p>
<p>Before reading this article, I was creating a K8S secret with the ACR information to access the images per subscription/namespace. If this can be done using across multiple subscriptions, that would be really nice.</p>
<p>Thanks,</p>
<p>Edward</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Peter K		</title>
		<link>https://pixelrobots.co.uk/2019/03/create-an-azure-container-registry-and-allow-aks-access/#comment-314</link>

		<dc:creator><![CDATA[Peter K]]></dc:creator>
		<pubDate>Tue, 19 Mar 2019 13:13:09 +0000</pubDate>
		<guid isPermaLink="false">https://pixelrobots.co.uk/?p=32690#comment-314</guid>

					<description><![CDATA[Great post! Not the first time I&#039;ve been visiting it for help.]]></description>
			<content:encoded><![CDATA[<p>Great post! Not the first time I&#8217;ve been visiting it for help.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
