Changes between Version 7 and Version 8 of k8snetworking2023

Timestamp:

Dec 8, 2023, 3:16:32 PM (5 months ago)

Author:

admin

Comment:

--

k8snetworking2023

@@ -34 +34 @@
 kind: IPAddressPool
 metadata:
-name: ippool
+  name: ippool
   namespace: metallb-system
 spec:
@@ -42 +42 @@
 }}}
 
-Replace 192.168.1.240-192.168.1.250 with your desired IP range.
+Replace IP ranges with your desired IP range.
 
 Apply the Pool:
@@ -48 +48 @@
 `kubectl apply -f metallb-pool.yaml`
 
-''2. Create a L2 Advertisement: When additional IP ranges are defined in the config- map, they need to be advertised on to the network. Create a file named L2add.yaml with the following content:''
+''2. Create a L2 Advertisement: When additional IP ranges are defined in the config- map, they need to be advertised on to the network. Create a file named `L2add.yaml` with the following content:''
 
 {{{
@@ -55 +55 @@
 kind: L2Advertisement
 metadata:
-  name: example
+  name: l2ads
   namespace: metallb-system
 spec:
@@ -92 +92 @@
 Check the Service:
 
-kubectl get svc wordpress-service
+`kubectl get svc wordpress`
 
 ''3. MetalLB will assign an external IP from the defined range to your service.''
@@ -165 +165 @@
 metadata:
   name: webapp-ingress
+  annotations:
+    nginx.ingress.kubernetes.io/rewrite-target: /
 spec:
   ingressClassName: nginx
   rules:
-  - host:
-     http: 
-        paths:
-        - path: /
+  - http:
+      paths:
+      - path: /webapp
         pathType: Prefix
         backend:
-            service:
-               name: webapp-nodeport-service
-               port:
-                   number: 80
+          service:
+            name: webapp-nodeport-service
+            port:
+              number: 80
 }}}
 
@@ -205 +206 @@
 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.
+Check IP issued from the load balancer
+
+`kubectl get svc --all-namespaces`
+
 
 === Step 4: DNS Configuration ===