<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity on GeekyRyan</title><link>https://rnemeth90.github.io/tags/identity/</link><description>Recent content in Identity on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 13 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/identity/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating AKS Workloads to Azure Workload Identity</title><link>https://rnemeth90.github.io/projects/2023-06-13-aks-workload-identity-migration/</link><pubDate>Tue, 13 Jun 2023 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2023-06-13-aks-workload-identity-migration/</guid><description>&lt;p&gt;For a long time, the standard way for a pod in AKS to authenticate to Azure resources (Key Vault, databases, service bus, etc.) was some flavor of managed identity binding via a sidecar (AAD Pod Identity), or worse, credentials baked into a secret. Azure Workload Identity is the modern replacement: it federates a Kubernetes service account with an Azure AD identity using OIDC, with no secrets to manage or rotate.&lt;/p&gt;</description></item></channel></rss>