|
Update the application with a rolling update strategy that releases new pods more gradually, one pod at a time.
Roll back the application to a specific version of the deploy history using the deployment.
Run the command without --restart=Never (Deploy ASP.NET Core Application images in Kubernetes (K8s) & POD). Command to create a simple deployment
kubectl run frontendmvcv1 --image=makader/myapp:frontendmvc-v1 --port 80
kubectl get deployment frontendmvcv1
Deploying the pods (individually or with a replication controller), using the same labels, except for the version, for which you use the value v2.
Modified the code (frontendmvc).
Build the image, re name the image tag version 2 & publish the image to Docker Hub
docker build -t frontendmvc .
docker tag frontendmvc makader/myapp:frontendmvc-v2
docker push makader/myapp:frontendmvc-v2
Execute the command "kubectl describe pod myapp-rc-wl284", each of them is running on a specific IP, internal to the node.
The Node IP (192.168.65.3), but you can’t access it directly because the forwarding rule to send the requests from the node IP to the pod IP is missing.
Create new ASP.NET Core MVC application through Visual Studio with Dockerfile.
OR Using Visual Studio Code, type "code .". Install the VSC extension named Docker by Microsoft, which help us to edit the Docker files.
OR Create by .NET Core CLI
Create new folder c:\frontendmvc, use powershell to run the below commands
- mkdir c:\frontendmvc
- cd c:\frontendmvc
- dotnet new mvc
- dotnet run
MS Dynamics CRM Contributor