Changes between Version 3 and Version 4 of k8snetworking2023

Timestamp:

Dec 7, 2023, 7:47:24 AM (12 months ago)

Author:

deepthi

Comment:

--

k8snetworking2023

@@ -144 +144 @@
       protocol: TCP
 }}}
+
+This service will expose your webapp on a NodePort.
+
+• Apply the Service:
+
+`kubectl apply -f [your-service-file].yaml`
+
+'''Step 2: Set Up Ingress to Route to the NodePort Service'''
+
+1. Define an Ingress Resource: Create an Ingress resource that routes traffic to your NodePort service. Here's an example YAML for the Ingress:
+
+{{{
+
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: webapp-ingress
+spec:
+  ingressClassName: nginx
+  rules:
+  - host:
+     http: 
+        paths:
+        - path: /
+        pathType: Prefix
+        backend:
+            service:
+               name: webapp-nodeport-service
+               port:
+                   number: 80
+}}}
+
+This Ingress resource routes traffic from nginx-ingress controller external IP to the webapp-nodeport-service on port 80.
+
+• Apply the Ingress Resource:
+
+`kubectl apply -f webapp-ingress.yaml`
+
+
+'''Step 3: Ensure Ingress Controller is Set Up Correctly'''
+
+Ensuring that your Ingress Controller is properly set up and accessible from outside the Kubernetes cluster involves several key steps. This setup is crucial for allowing external traffic to reach your services through the Ingress rules you've defined. Here's a breakdown of what this entails:
+
+1. Deploying the Ingress Controller
+
+• Choose an Ingress Controller: There are several Ingress Controllers available, such as NGINX, Traefik, HAProxy, etc. NGINIX is a popular choice due to its stability and feature set.
+
+• Install the Ingress Controller: You need to deploy the Ingress Controller in your Kubernetes cluster. For NGINX, you might use a command like:
+
+{{{
+kubectl apply -f
+https://raw.githubusercontent.com/kubernetes/ingress-
+nginx/controller-
+v1.8.2/deploy/static/provider/cloud/deploy.yaml
+}}}
+
+2. Exposing the Ingress Controller
+
+
+• Service Type: The Ingress Controller itself is exposed via a Kubernetes Service. This Service needs to be accessible from outside the cluster. There are two common ways to do this:
+- NodePort: The Service is exposed on a high port (e.g., 30000-32767) on each node's IP address. External traffic can reach the Ingress Controller by hitting any node's IP at this port.
+- LoadBalancer: If your cluster is running in a cloud environment that supports LoadBalancer Services, this is a more straightforward way to expose your Ingress Controller. For our setup lets allow the metalLB setup to lease an external IP address that routes traffic to the Ingress Controller.
+
+'''Step 4: DNS Configuration'''
+
+1. Configure DNS: Map the DNS record to the external IP address of one of your cluster nodes (if using NodePort for the Ingress Controller) or to the external IP provided by the LoadBalancer (if using LoadBalancer for the Ingress Controller).
+
+Read More:
+[https://spacelift.io/blog/kubernetes-ingress]
+[https://matthewpalmer.net/kubernetes-app-developer/articles/kubernetes-ingress-guide-nginx- example.html]
+