create apigateway using cluster IP chat health

CharlyJazz · Nov 24, 2023 · ac3ff0a · ac3ff0a
1 parent 9f0346c
commit ac3ff0a
Showing 9 changed files with 56 additions and 6 deletions.
diff --git a/api-gateway/README.md b/api-gateway/README.md
@@ -71,3 +71,5 @@ List the pods the load balancer pointing to.
 Make sure that probes (ie. readiness, liveness) are configured.
 Describe the pods ( kubectl describe pods <pod_name> -n <namespace>) to see why the health check is failing.
 Fix the health check problem. Once the pods are healthy, give the load balancer some time (sometimes it takes hours) to update the status.
+
+https://medium.com/google-developer-experts/getting-started-with-gke-gateway-controller-ee45c3bc8996
diff --git a/api-gateway/auth-http-route.yaml b/api-gateway/auth-http-route.yaml
@@ -5,7 +5,7 @@ metadata:
 spec:
   parentRefs:
   - kind: Gateway
-    name: global-external-managed-chat-api-gateway
+    name: gke-l7-gxlb-api-gateway
   rules:
     - matches:
         - path:

diff --git a/api-gateway/chat-health-check-policy.yaml b/api-gateway/chat-health-check-policy.yaml
@@ -0,0 +1,19 @@
+apiVersion: networking.gke.io/v1
+kind: HealthCheckPolicy
+metadata:
+  name: chat-healthcheck
+spec:
+  default:
+    checkIntervalSec: 10
+    timeoutSec: 10
+    logConfig:
+      enabled: true
+    config:
+      type: HTTP
+      httpHealthCheck:
+        port: 9000  
+        requestPath: /api/health/
+  targetRef:
+    group: ""
+    kind: Service
+    name: chat-microservice-service
diff --git a/api-gateway/chat-http-route.yaml b/api-gateway/chat-http-route.yaml
@@ -0,0 +1,17 @@
+apiVersion: gateway.networking.k8s.io/v1beta1
+kind: HTTPRoute
+metadata:
+  name: chat-http-route
+spec:
+  parentRefs:
+  - kind: Gateway
+    name: gke-l7-gxlb-api-gateway
+  rules:
+    - matches:
+        - path:
+            type: PathPrefix
+            value: /chat
+      backendRefs:
+        - kind: Service
+          name: chat-microservice-service
+          port: 9000
diff --git a/api-gateway/gateway.yaml b/api-gateway/gateway.yaml
@@ -1,9 +1,9 @@
 apiVersion: gateway.networking.k8s.io/v1beta1
 kind: Gateway
 metadata:
-  name: global-external-managed-chat-api-gateway
+  name: gke-l7-gxlb-api-gateway
 spec:
-  gatewayClassName: gke-l7-global-external-managed 
+  gatewayClassName: gke-l7-gxlb # Probar este
   listeners:
   - name: http-listener
     protocol: HTTP

diff --git a/auth-microservice/k8s/auth-db-service.yaml b/auth-microservice/k8s/auth-db-service.yaml
@@ -6,7 +6,7 @@ metadata:
     name: auth-db-service
     app: database
 spec:
-  type: LoadBalancer
+  type: ClusterIP
   ports:
       - port: 5432
         targetPort: 5432

diff --git a/chat-microservice/k8s/cassandra-service.yaml b/chat-microservice/k8s/cassandra-service.yaml
@@ -6,7 +6,7 @@ metadata:
     name: chat-db-service
     app: database
 spec:
-  type: LoadBalancer
+  type: ClusterIP
   ports:
       - port: 9042
         targetPort: 9042

diff --git a/chat-microservice/k8s/chat-microservice-deployment.yaml b/chat-microservice/k8s/chat-microservice-deployment.yaml
@@ -18,6 +18,18 @@ spec:
         - name: chat-microservice
           image: charlyjazz/chat-microservice:latest
           imagePullPolicy: Always
+          livenessProbe:
+            initialDelaySeconds: 60
+            httpGet:
+              path: /api/health/
+              scheme: HTTP
+              port: 9000
+          readinessProbe:
+            initialDelaySeconds: 60
+            httpGet:
+              path: /api/health/
+              scheme: HTTP
+              port: 9000
           ports:
           - containerPort: 9000
             hostPort: 9000

diff --git a/chat-microservice/k8s/chat-microservice-service.yaml b/chat-microservice/k8s/chat-microservice-service.yaml
@@ -6,7 +6,7 @@ metadata:
     name: chat-microservice-service
     app: microservice
 spec:
-  type: LoadBalancer
+  type: ClusterIP
   ports:
     - port: 9000
       targetPort: 9000