Search for a command to run...
I used to be a .NET developer. Nowaways, I am a DevOps solutions architect with a focus on Azure and Kubernetes.
I also love productivity topics, especially when it comes to doing more with less of my time. I'm also a daddy, so time is a limited resource for me.
No comments yet. Be the first to comment.
I'm going to share all my secrets with you
Using a pull-request workflow
This is the guide I wish I had
Connecting your GitHub Workflows to Azure AD using OpenID Connect
In this post, I’ll walk through the essentials of configuring an AKS cluster to use Argo CD with an NGINX Ingress Controller. Pre-Requisites You’ll need: An AKS cluster. Here’s a Gist I use to create a simple cluster. Helm 3 Azure CLI A Custom DNS/A...
It might not be obvious, and certainly when I got started with containers, I didn’t realize that there’s side-benefits that are not typically talked about.
You might know the main benefits already,
In short, because they are lightweight, they have all the benefits from VMs and they are fast to start. This small difference opens a new world of possibilities.
Since they are fast to start and they are portable, with some work you can run the entire application from the CI/CD pipelines. This opens new possibilities for things that were once much harder to do - running functional tests before deploying anywhere.
In the example above, we run functional smoke tests against a docker compose version of the application, database and all. You can extend this concept to also run penetration tests as I alluded in my previous DevSecOps post.
What’s risky? What fails often? Database changes? API Authentication?
There are things you can probably test with containers without deploying to an environment and spending money on cloud resources.
