#aks

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 1 – Daniel's Tech Blog

6 days ago

Deep dive into enabling Cilium native routing on Azure Kubernetes Service with BYOCNI - a 3-part experiment:

Part 1: www.danielstechblog.io/an-experimen...

Part 2: www.danielstechblog.io/an-experimen...

Part 3: www.danielstechblog.io/an-experimen...

#Azure #AKS #Kubernetes #Cilium #Networking

1 1 0 0

Deploy Azure SQL with Private Endpoint and Test Connectivity from AKS This tutorial demonstrates how to: Create networking for AKS Deploy an AKS cluster using Azure CNI...

1 week ago

Deploy Azure SQL with Private Endpoint and Test Connectivity from AKS This tutorial demonstrates how to: Create networking for AKS Deploy an AKS cluster using Azure CNI Overlay Deploy Azure SQL Dat...

#aks #azure #devops #cloud

Origin | Interest | Match

0 0 0 0

Michael Durkan - Microsoft Azure MVP

@durkanm.bsky.social

1 week ago

AKS Networking – Ingress and Egress Traffic Flow In the previous post on AKS Networking, we explored the different networking models available in AKS and how IP strategy, node pool scaling, and control plane connectivity shape a production-ready …

Most AKS networking issues aren’t Kubernetes problems — they’re traffic flow problems nobody mapped before deployment.

Plan ingress & egress early to avoid security gaps and performance issues.

michaeldurkan.com/20...

#Azure #AKS #Kubernetes #Networking #MVPbuzz

0 0 0 1

Codit

@coditcompany.bsky.social

1 week ago

Blog posts | Codit

Kubernetes gives you flexibility, but keeping clusters secure, stable, and up to date is the real challenge. AKS helps simplify upgrades and future-proof your platform.
Read more 👇
ow.ly/K5jQ50YmZ1q‑proofing-you...
#Kubernetes #AKS #DevOps

1 0 0 0

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 3 – Daniel's Tech Blog

1 week ago

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 3 www.danielstechblog.io/an-experimen... #Azure #AKS #Kubernetes #Cilium

1 0 0 0

Leutzscher

@leutzscher68.bsky.social

2 weeks ago

Enttäuschung pur. Von „Brennen im Herzen“ nichts zu sehen. #AKS #ChemieLeipzig Emotionslos, kein Kampf, kein Aufbäumen… so steigt man sang und klanglos ab.

4 0 1 1

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 2 – Daniel's Tech Blog

2 weeks ago

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 2 www.danielstechblog.io/an-experimen... #Azure #AKS #Kubernetes #Cilium

0 0 0 0

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 1 – Daniel's Tech Blog

2 weeks ago

An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 1 www.danielstechblog.io/an-experimen... #Azure #AKS #Kubernetes #Cilium

0 0 0 0

@leutzscher68.bsky.social

2 weeks ago

Build Auto-Migration Systems for Azure Spot VMs in AKS Build automated migration systems to handle Azure Spot VM evictions in AKS, keeping workloads running within the 30-second window.

#Cloud #AKS #Cluster #Autoscaler #Karpenter #Kubernetes #Spot #VMs

Origin | Interest | Match

0 0 0 0

Leutzscher

2 weeks ago

Moin. Bis zum Wochenende steht Sonne satt auf dem Programm. Endlich wieder Sportpark, endlich wieder Fußball pur. Wird auch Zeit. #AKS #ChemieLeipzig

3 0 1 0

Joey Chen

@joeyc-dev.bsky.social

2 weeks ago

Set up volumes accessing cross-tenant Azure Storage without account access keys in Azure Kubernetes Service - Joey Chen Learn how to create Kubernetes volumes with Azure storage in different tenant without setting up account access key in Azure Kubernetes Service (AKS).

👉 New post: Access Azure Storage across tenants in AKS—no access keys needed 🚀
Securely mount K8s volumes via BlobFuse (Workload Identity) or NFS for Azure Fileshare/Blob. Step-by-step guide with examples!

🔗 Link: blog.joeyc.dev/posts/aks-no...

#Azure #AKS #Kubernetes #DevOps #CloudSecurity

0 0 0 0

Steve Buchanan

@buchatech.bsky.social

2 weeks ago

I’m back on @RunAsRadio for round 3! 🎧

It was great to catch up with Richard Campbell about #multicloud #SaaS.

We dig into:
🔹 Getting SaaS workloads to #Azure #AKS
🔹 #Kubernetes as the bridge
🔹 #OpenTofu, #Prometheus, & more

runasradio.com/Shows/Show/1...

#MVPBuzz #DockerCaptain #Jamf

2 0 0 0

Pixel Robots. ☁️☸️ (Richard Hooper)

@pixelrobots.co.uk

2 weeks ago

With NGINX Ingress retirement hitting next month, a lot of people are asking: "What's next?" 🤔

I have been recommending Envoy Gateway, so thought I'd better spend some time documenting what actually works on AKS.

Check it out at: buff.ly/WRXfSNa

#Kubernetes #AKS #Azure #EnvoyGateway #GatewayAPI

1 0 0 0

AKS Node Pool Rollback Now in Preview URL has been copied successfully! URL has been copied successfully! Share: Reading Time: 4 minutes We’ve all been there. You upgrade a node pool, something breaks in production, and you’re left deciding whether to push forward with a fix or try to undo what you just did. Until recently, “undoing” a Kubernetes version upgrade in AKS wasn’t a first-class operation. You’d be looking at manual workarounds or blue-green setups to recover. The new node pool rollback feature landing in AKS preview is useful because it gives you a proper recovery path without any of that. A merged PR in the Azure CLI extensions repo (#9314) adds two new commands to `aks-preview`: `az aks nodepool rollback` and `az aks nodepool get-rollback-versions`. Here’s what they do and when you’d want to use them. ## What Is Node Pool Rollback? The feature lets you revert a node pool back to the Kubernetes version and node image it was running before an upgrade. Both the orchestrator version and the node image (VHD) get rolled back together, so you’re not left in a mixed state. It’s worth being clear about what this is and isn’t. It’s a version rollback, not a full state restore. Workload changes, config changes, and anything else outside of the node pool version are not affected. Think of it as an escape hatch for when an upgrade itself goes sideways. Key things to know upfront: * Only available for **seven days** after an upgrade completes * Only goes back **one step** – no chaining rollbacks to skip multiple versions * No concurrent cluster operations during rollback * You must **disable cluster autoupgrade** first, or it’ll just re-upgrade after you roll back * Can’t roll back to a version that’s out of AKS support ## Prerequisites You’ll need the `aks-preview` CLI extension at the latest version and Azure CLI 2.64.0 or higher: Shell # Install or update the extension az extension add --name aks-preview az extension update --name aks-preview # Verify your CLI version az --version 123456 | # Install or update the extensionaz extension add --name aks-previewaz extension update --name aks-preview # Verify your CLI versionaz --version ---|--- The feature requires API version `2025-08-02-preview` or later under the hood, but as long as you’re running a current `aks-preview` extension you’ll be covered. ## The New Commands ### Checking What You Can Roll Back To Before pulling the trigger, you can see what rollback versions are available for a node pool: Shell az aks nodepool get-rollback-versions \ --name myNodePool \ --cluster-name myAKSCluster \ --resource-group myResourceGroup 1234 | az aks nodepool get-rollback-versions \ --name myNodePool \ --cluster-name myAKSCluster \ --resource-group myResourceGroup ---|--- This queries the upgrade profile and surfaces the previously used versions. If the node pool hasn’t been upgraded at least once, there’s nothing to roll back to and the command will tell you so rather than returning a silent empty result. ### Performing the Rollback Once you’ve confirmed there’s a version to go back to: Shell az aks nodepool rollback \ --name myNodePool \ --cluster-name myAKSCluster \ --resource-group myResourceGroup 1234 | az aks nodepool rollback \ --name myNodePool \ --cluster-name myAKSCluster \ --resource-group myResourceGroup ---|--- That’s it. The rollback process is manual to trigger but fully automatic once started. AKS handles rolling all the nodes back to the previous version state. It’s all-or-nothing: if any node fails to roll back, the whole operation fails. This keeps the cluster in a clearly defined state rather than leaving you with a partially rolled-back pool. ## Monitoring the Rollback The two most useful options are the **Activity Log** on the cluster in the Azure portal and the **Operation Status API** for real-time updates via REST. The rollback shows up as a standard AKS operation, so your existing alerting should pick it up. ## When Should You Actually Use This? The sweet spot for this feature is production incidents where you’ve upgraded a node pool and something breaks that you can’t quickly fix. Application compatibility issues, unexpected performance regressions, or infrastructure weirdness that wasn’t caught in pre-prod. What it’s not good for: staying on an older version indefinitely. Rollback is a temporary recovery tool. Security patches and updates come with newer versions, and rolling back exposes you to whatever vulnerabilities were addressed in the upgrade. Treat it as breathing room while you fix the underlying issue, then re-upgrade. The guidance suggests re-upgrading within days for critical security issues, within weeks for app compatibility problems, and no more than 30 days in any case. One gotcha worth flagging: if your cluster is part of an Azure Kubernetes Fleet Manager autoupgrade profile, you need to remove it from the update group before rolling back. Otherwise Fleet Manager will just upgrade it again right after. ## What About Node Image-Only Rollback? Worth knowing: if you ran a node image update (not a full Kubernetes version upgrade) within the last seven days, rollback will restore the previous VHD image while keeping the same Kubernetes version. So this isn’t limited to full version upgrades. Handy if a bad node image slips through. ## Wrapping Up The node pool rollback capability fills a real gap in the AKS upgrade story. It won’t replace solid upgrade strategies like blue-green node pools or proper pre-prod testing, but it gives teams a genuine recovery path when production upgrades don’t go to plan. It’s currently in preview and requires the `aks-preview` extension, so treat it accordingly in production environments. Worth getting familiar with before you need it though. For more detail on the capabilities and limitations, the official AKS rollback docs are worth a read. Share:

2 weeks ago

AKS Node Pool Rollback Now in Preview Reading Time: 3 minutesWe’ve all been there. You upgrade a node pool, something breaks in production, and you’re left deciding whether to push forward with...

#Community #AKS #Azure #Azure #Kubernetes #Service #kubernetes

Origin | Interest | Match

0 0 0 0

devopstales

@devopstales.bsky.social

3 weeks ago

⚠️ Azure Key Vault + AKS integration gotchas you NEED to know.

From identity config to network policies — here's how to fix the most common integration failures.

#Azure #AKS #KeyVault #Kubernetes #CloudSecurity
🔗 devopstales.github.io/cloud/azure-...

0 0 0 0

devopstales

@devopstales.bsky.social

3 weeks ago

🌐 Production-ready ingress on AKS: Configure custom SSL certs + DNS with Nginx Ingress Controller.

Automate cert-manager, external-dns, and Azure DNS integration.

#AKS #Nginx #Ingress #SSL #Kubernetes #Azure
🔗 devopstales.github.io/kubernetes/n...

1 0 0 0

Roy Kim

@roykim1.bsky.social

3 weeks ago

aks-demos/aks-kaito at main · RoyKimYYZ/aks-demos Azure Kubernetes Demos for the purposes of sharing my knowledge to the technology community - RoyKimYYZ/aks-demos

Want to run LLMs on AKS without the infrastructure headache? 🚀
Check out my repo: 🔗
github.com/RoyKimYYZ/ak...
✅ Automated GPU provisioning
✅ One-click OSS model deployment (Phi, Llama, Falcon)
✅ Private & secure inference endpoints
#AKS #Kubernetes #Azure #GenerativeAI #LLMOps #KAITO #mvpbuzz

1 0 1 0

EkasCloud – Personalized Training Platform

@ekascloud.bsky.social

3 weeks ago

DevOps with Azure Cloud DevOps methodology gives you a complete view of the entire software development lifecycle. Azure DevOps Certification from EkasCloud is handled by industry professionals, depending on large-scale b...

DevOps with Azure Cloud
www.ekascloud.com/training-cou...
#DevOps #AzureDevOps #MicrosoftAzure #CloudComputing
#CICD #Automation #AKS #InfrastructureAsCode
#DevOpsEngineer #CloudEngineer #TechCareers
#FutureSkills #Ekascloud #LearnDevOps #AzureCloud

1 0 0 0

Pixel Robots. ☁️☸️ (Richard Hooper)

@pixelrobots.co.uk

3 weeks ago

🚨 Starting in ~30 mins: AKS Community Call!
Join to hear the latest updates, roadmap insights, and connect directly with the Azure Kubernetes Service team. Great chance to learn what’s coming next and ask questions live.

👉 blog.aks.azure.com/webinars/

#AKS #Azure #Kubernetes #CloudNative

0 0 0 0

Michael Durkan - Microsoft Azure MVP

@durkanm.bsky.social

3 weeks ago

AKS Networking – Which model should you choose? In the previous post, we broke down AKS Architecture Fundamentals — control plane vs data plane, node pools, availability zones, and early production guardrails. Now we move into one of the most co…

AKS networking is a Day 1 decision. Get it wrong and it’s hard to change later. IP exhaustion or performance issues can force a rebuild.

Overlay = scalable & IP-efficient.

Node Subnet = direct connectivity but higher IP usage.

tinyurl.com/4nj9m8bf

#Azure #AKS #Networking

0 0 0 0

3 weeks ago

Doc Ingestion CLI for AKS KAITO RAG Engine After deploying AKS KAITO Retrieval Augmented Generation (RAG) Engine withe an embeddings model, I tested with many curl commands to index, update and que...

#Community #AI #AKS #Azure #kubernetes #rag

Origin | Interest | Match

0 0 0 0