This is a follow-up to my post about the Kubernetes Cluster running on Azure Stack. In that post, I asked myself how to scale a deployed cluster and how to update the cluster. Since that post went live, I’ve done experimentation on my own, and also learned a few things about the deployment toolset being used for the Kubernetes Cluster Template.
The 100th episode of Buffer Overflow – a weekly tech news podcast I host – is steadily approaching. As I write this, we are getting ready to record episode 98. In preparation for the 100th episode, I thought it might be nice to look over past episodes and find some common themes, running gags, and anything else that caught my eye. At an average of 35 minutes, that’s roughly 57 hours of combined audio. There’s no way I could listen to the entirety of the episodes, and so I started thinking. What if I could transcribe the audio to text, and then search through the text to find all the times we talked about Derrick and Miranda, how we’re all doomed, or smiling poop? The Azure Speech to Text API can be used to convert speech to text of audio files. Why not start there?
If you’ve been test driving Azure Stack with a full stamp or just the ASDK, you may have decided to try out the Kubernetes Cluster template that is available in the marketplace syndication. This post is meant to walk through what the K8s template is, what it isn’t, and how it works.
In case you didn’t notice, the Day Two Cloud podcast has officially launched! Big thanks to Tim Warner and Kenny Lowe for being the guests in the first two episodes! There is a lot more great content coming. I’ve got ten more episodes already recorded, and two more scheduled. If I stick to a fortnightly schedule for publishing, that should take me through July. That is pretty ridiculous!!! Needless to say that I am already considering moving to a weekly schedule.
I’ve had a few people ask me about where the podcast is hosted, what topics I might be interested in, and what my process is for publishing. The process for recording and publishing is a whole post unto itself, but I can address the other two topics here.
This is the second and probably final post in this series. If you haven’t read the first post I would highly recommend it. When we last left our erstwhile heroes, they had successfully setup the Azure authentication method on a Vault server and created a policy associated with a role in the Azure auth method. The policy grants access to a key-value store called webkv. Now comes the fun part, how does an Azure VM go about using the Azure auth method to access the secrets stored in webkv? So glad you asked!