Kubernetes Lessons Learned

ASP.NET CORE and Docker

ASP.NET Core Application with Docker

Add SQL Server 2017 Docker Container to ASP.NET Core MVC/Web API Project

Docker Compose

Deploy ASP.NET Core Application images in Kubernetes (K8s) & POD

Kubernetes ReplicationController

Access ASP.NET Core MVC Application with Kubernetes and NodePort

Create a Kubernetes service using a YAML

Deploy ASP.NET CORE application with the Kubernetes Deployments

Kubernetes ReplicaSet selector with matchExpressions

Kubernetes Deployment Update Strategy

Create a Kubernetes service using a YAML

Instead of exposing directly (see the blog), create a service in a declarative way using a YAML file

forntendmvc_service .yaml

--- 
apiVersion: v1
kind: Service
metadata: 
 name: myapp-svc
spec: 
  selector:
    app:myapp
  type: NodePort
  ports:
    - port:80
      nodePort: 30001

Access ASP.NET Core MVC Application with Kubernetes and NodePort

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.

Kubernetes Service Type using -type options

The command to expose the replication controller 

kubectl expose rc myapp-rc --name=myapp-rc-service --type=NodePort

The --name option sets a name for the service. 
The --type option sets the service type, and can be one of the following four values:

• ClusterIP: The default value that exposes the pods internal to the cluster. 
• NodePort: Exposes the pods as a static port on each node that contains the pods
• LoadBalancer: Exposes the pods externally using a load balancer of a cloud provider. 
• ExternalName: Available from version 1.7 of kube-dns to expose the pods through the contents of the externalName field.