Service

• We have create an nginx-replica set with 3 pods and a service
  
  
• The endpoints are update to kube-proxy
  
• kubernetes allows service to be accessed within clusters
• We can access service by name or by ip address from containers
• The fqdn for service is <service-name>.<namespace>.svc.cluster.local
  

Node Port

• Node Port type of service exposes the kubernetes services over Port as shown below
  
• Refer Here for the changeset
• Apply the service
  
  
• Other Service Types:
  • LoadBalancer
  • External

Controllers to control rollouts

• Here we have
  • Deployments
  • Daemonsets
  • Statefulsets
• These things when we combine with service, we can give zero down time deployments.
• Topics for next week
  • Healthchecks for service
  • Deployments
  • Daemonsets
  • Statefulset
  • Managed K8s Services
    • AKS
    • EKS
  • Service with Load Balancers
  • ConfigMaps & Secrets
  • Ingress
  • Storage
    • Storage Classes
    • PVC
  • Kustomize & helm

Exercises

• Create a nopcommerce pod with the following
  • environmental variables:
    • purpose = learning
• Create a namespace called as dev and create the nop commerce pod in dev namespace
• Create a nginx rs with service in default namespace and create a nginx res with service in dev namespace
• Create a pod called as c1 with alpine in it (default), try accessing the service in default namespace as well as dev namespace