Thanks a lot for sharing! You explained very clearly and nicely. I have one doubt, does anyone know after the first pod that mounts the secret how to get the key vault value into the other pods env?
Good video. This pod is created just to check the secret right, for another application pods we dont need to do anything right. It will get connected with password?
i am planning to connect multiple instance to central keyvault in your demo you are added vm scaleset instead of that can i use azure service principal id or userAssignedIdentityID if yes can you please provide those steps
Awesome but a quick question. I understand this tutorial uses “managed identity” to authenticate keyvault service. Can we use any other credential auth mechanism for AKS ? Also what could be the design reason for managed identity access to vmss instead of whole aks service(hosting vmms) ?
Excellent video! I like how you first described the overall process at 4:30 before conducting the demo. Thank you!
Thanks buddy, thats a cool explanation and a realtime example.
Very clear explanation and moreover, you demo it which is awesome
Very GOOD! Only video/article that worked for me
Simple and beautiful, I loved this explanation.
Awesome video - Could you also suggest, alternative way to avoid mounting ?
Thanks a lot for sharing! You explained very clearly and nicely. I have one doubt, does anyone know after the first pod that mounts the secret how to get the key vault value into the other pods env?
Very informative video. Can we also have the video for managed identity :)
Excellent explanation. Thank you
Very informative! Thanks a lot.
Awesome video! great job!
Good video. This pod is created just to check the secret right, for another application pods we dont need to do anything right. It will get connected with password?
Can we use azure vault to store certificate and use it with aks ingress for ssl termination?
i am planning to connect multiple instance to central keyvault in your demo you are added vm scaleset instead of that can i use azure service principal id or userAssignedIdentityID if yes can you please provide those steps
Good explanation
How can i implement the secret rotation policy on AKS?
Very helpful, thanks!
Hello Will the similar process follow for Azure redhat openshift
Awesome but a quick question. I understand this tutorial uses “managed identity” to authenticate keyvault service. Can we use any other credential auth mechanism for AKS ?
Also what could be the design reason for managed identity access to vmss instead of whole aks service(hosting vmms) ?
good explanation. i am looking someone who can teach me complete aks with devops pipeline
Hi is it safe to use this busybox image from google container registry ?
Mate, any idea on implementing the final pod deployment using terraform?
bhai ye mate word use krke cool banne ki koshish mt kia kr, australian nahi h tu, ek chutiya ldka h tu yaad rakhio
great demo
Awesome, kudos to you
How to set an environment variable from this secretProviderClass to the container?
Hi! Did you manage to achieve this? I have the same doubt :(. If you run a new pod... how can you read/add the secret value in the env?
Once text file is mounted and accessible inside pod - you can run add it to init script using linux export command
Were you able to figure out this.
Thanks for sharing your knowledge. If you have a time please share some real time issues and solutions on AKS.
Sure, I will try to make a video on real time issues after this AKS series.
Well Done :)