Changes between Version 2 and Version 3 of k8snetworking2023

Timestamp:

Dec 7, 2023, 7:41:30 AM (2 years ago)

Author:

deepthi

Comment:

--

k8snetworking2023

@@ -59 +59 @@
   - ippool
 }}}
+
+Apply the advertisement:
+
+`kubectl apply -f L2add.yaml`
+
+'''Step 3: Create a Service with a Virtual IP'''
+
+Let’s expose the wordpress application: Edit the service of type LoadBalancer on
+wordpress-service.yaml:
+
+{{{
+apiVersion: v1
+kind: Service
+metadata:
+  name: wordpress
+spec:
+  selector:
+    app: wordpress
+  ports:
+    - protocol: TCP
+port: 80
+      targetPort: 80
+  type: LoadBalancer
+}}}
+
+Save and apply it:
+
+`kubectl apply -f wordpress-service.yaml`
+
+Check the Service:
+
+kubectl get svc wordpress-service
+
+3. MetalLB will assign an external IP from the defined range to your service.
+
+'''Step 4: Access the Service'''
+
+• You can now access the wordpress server using the external IP provided by MetalLB. This IP is accessible within your network.
+
+'''Troubleshoot'''
+
+On a different VM than the master do the testing for ARP advertisements.
+
+Remove MetalLB (Only for the reference)
+
+{{{
+arp -a
+ping 192.168.1.200
+sudo apt install iputils-arping
+arping 192.168.1.200
+}}}
+
+Remove MetalLB (Only for the reference)
+
+{{{
+kubectl delete -f
+https://raw.githubusercontent.com/metallb/metallb/v0.13.12/con
+fig/manifests/metallb-native.yaml
+kubectl delete -f metallb-pool.yaml
+kubectl delete -f L2add.yaml
+kubectl get all -n metallb-system
+}}}
+
+=== Kubernetes Ingress. (Optional) ===
+
+In a Kubernetes environment, if you want to use an Ingress resource to direct traffic to a service that's exposed via NodePort, while still allowing users to access the service using a standard port (like port 80) without specifying the NodePort, you can set it up as follows:
+
+'''Step 1: Expose Your Service Using NodePort'''
+
+1. Create a Service of Type NodePort for Your Web Application: Suppose you have a deployment named webapp. You'll need to create a service for it. Here's an example YAML for the service:
+
+{{{
+apiVersion: v1
+kind: Service
+metadata:
+  name: webapp-nodeport-service
+spec:
+  type: NodePort
+  selector:
+    app: webapp
+  ports:
+    - port: 80
+      targetPort: 80
+      protocol: TCP
+}}}