Timeout issues deploying to a continuous web job
Some time ago I wrote about how to create a YAML Azure DevOps pipeline to deploy a .NET framework v1 webjob.
azure
A collection of 59 posts
Automated upgrades using Flux
GitOps allows us describe our running environment from a Git repo. We are able to state the deployments and the Helm charts that should be part of a Kubernetes cluster. As such, we can declaratively specify the version of these...
User Assigned Identity using an ARM template for an App Service
Managed identities on Azure are great. No need to store client secrets corresponding to a service principal. Instead, we let Azure worry about that. We can let compute resources (like app services) authenticate against Azure AD to use other Azure...
Building and pushing a container to a registry with environment/git commit tag
One way to implement promotions in GitOps is to have the operator deploy images published with a prefixed environment tag. For example, if you want your operator in your staging cluster to deploy only images ready for staging, you can...
Configuring Flux to use Helm charts from Azure Container Registry
Flux watches a Git repository containing Kubernetes manifests and it applies changes to the cluster. Realistically, you will also use Helm charts. You can install the Flux Helm operator so that you can declare what Helm charts should be installed...