Azure Container Apps Secrets Explained

You should secrets to store all the sensitive information of the app, like connection strings and keys.
In this video, we are going to explore how secrets work Azure Container Apps!
00:00 Intro
00:33 Intro - Comparison
02:43 Intro - Few things to keep in mind
03:34 Demo - Deploy an app with secrets
07:01 Demo - Restart after changing a secret
08:31 Demo - Reusing Secrets
10:51 Demo - Reading through Console
11:41 ARM Templates
Source Repo - github.com/KamalRathnayake/Me...
Meet Kamal Today
Kamal Rathnayake

[@celkoken]

thank you so much for this

[@SnickersPlayaS]

I've got a setup with secret retrieval from KV using href, works when KV ingress is public however without having KV open to public it fails to setup complaining its unable to fetch the secret. I've whitelisted the container apps environment IP and allowed it access to KV using user-assigned managed identity. Do you know what the problem could be/what im missing?
Thank you.

[@MCchaosbrodog]

and when i update my secret in key vault how to apply that change to container app, it still reads the old secret

[@uniq-vlog]

Request for demo ACA with key vault

[@pranayamr]

What about Application Configurations , that can also help, can we use it ?

[@Steve3dot1416]

Excelent serie. But anyone who can access the shell of the container can see the secret, a production password for example. Is there any way to get the secret dynamicaly from within the code only?

[@AskarKopbayev]

use google distroless images for your containers. they don't have shell.