Posts

Pods' Scheduled Rollout with CronJob

First let's add role, service account and role binding: kind : ServiceAccount apiVersion : v1 metadata :   name : rest-api-deployment-restart-service   namespace : rest-api-ns-{{ .Values.environment }} --- apiVersion : rbac.authorization.k8s.io/v1 kind : Role metadata :   name : deployment-restart-role   namespace : rest-api-ns-{{ .Values.environment }} rules :   - apiGroups : [ "apps" , "extensions" ]     resources : [ "deployments" ]     resourceNames : [ "rest-api-deploy- {{ . Values . environment }} " ]     verbs : [ "get" , "patch" , "list" , "watch" ] --- apiVersion : rbac.authorization.k8s.io/v1 kind : RoleBinding metadata :   name : deployment-restart-role-binding   namespace : rest-api-ns-{{ .Values.environment }} roleRef :   apiGroup : rbac.authorization.k8s.io   kind : Role   name : deployment-restart-role subjects :   - kind : ServiceAccount     name : rest-api-deployment-restart-...

Publish Angular 2+ Application to Kubernetes Dev, QA, Prod Environments based config.json (not environments) using one base image

Publish ASP.NET Core 5 Application with Multiple Ingress Controllers in Azure Kubernetes Service (AKS) - CloudOps - PART 2

  Coming Soon... 

Migrating to PostgreSQL from Microsoft SQL Server

 Coming Soon... 

Publish ASP.NET Core 5 Application with Multiple Ingress Controllers in Azure Kubernetes Service (AKS) - Tracing, Monitoring, Logging, TLS and Custom Domain - PART 3

 Coming Soon... 

Publish ASP.NET Core 5 Application with Multiple Ingress Controllers in Azure Kubernetes Service (AKS) - Build and Deploy - PART 1

Image
1. Overall Architecture overview, components and tech stack Front-End: Angular 11 Back-End: ASP.NET Core 5 (API) Azure AKS (K8S ): 1.19 Azure ACR 2.   Create an AKS cluster I will skip this step, creation of the AKS cluster pretty straight forward on Azure, just follow the instructions:     3. Deploy ASP.NET Core API Create Image First, we have to add Dockerfile to our solution, I'm doing this from VS2019: My Dockerfile looks like the following: Here is the catch, VS2019 will add Dockers file to your Web Project, not the solution location. In case you have one project it will work fine, but in case you have multiple projects like I do, the docker build command will fail. In order to fix this you have to use the following docker build mentioned files  and project locations explicitly: Push Image to Azure Container Registry (ACR) Next, don't forget to log in to Azure ACR instance:  docker login xxx.azurecr.io And now we can tag and push the Image to Azure AC...