Material for a complete workshop Kubernetes on Azure
Let’s create and integrate an Angular app with Azure Active Directory Business to Consumers using the Authorization Code with Proof Key of Code Exchange flow.
Kubernetes is awesome, but can be a costly service to run. In many cases it pays off to take a look at the various components and settings to see if there are ways to save money.
So I finally decided to do it, after thinking about it at least a dozen times: I switched from using WordPress to Hugo for my blog. I watched most of my online friends do it too the last couple of years. And all but a few ended up with a static generated site (with Jekyll, GitHub Pages or Hugo) but were pretty excited about the results.
This post is about adding a widget to your Azure DevOps Dashboard showing the Dependency Track information on one or more of your projects.
Finding out about performance issues and collecting metrics on the usage of your app is important. Add Application Insights to your apps and let the reports tell you what is wrong and allow you to track all kinds of dimensions.
Canary deployments with just Azure DevOps. Well, with Azure DevOps and Azure Kubernetes Service. But that’s it, no additional software required.
October 1st, Pamela and I will be speaking at the Techorama Event in the Netherlands. We hope to see you there!
What are we trying to accomplish? Azure runs a very decent Kubernetes service these days. I have used it as the main infrastructure in a couple of projects and am quite impressed. Impressed enough to even suggest it as the target platform for our largest projects 😊
Say you want to use an Azure DevOps pipeline to build your containerized app. This scenario is of course supported and you would leverage all the built-in stuff (built-in container image, default container tasks, hosted build agent, etc.). You can even choose between the UI or YAML to configure the build pipeline.
Some notes on the final day @ LEAP! This was the final day and filled with various talks. For me the most interesting one today was related to the upcoming .NET 3.0 🙂