c031464f71
lionsctl pipeline generates manifests with port 8080 by default and doesn't respect custom port configuration in .lionsctl.yaml. Changing the application to use port 8080 fixes the health check failures. Changes: - application-prod.properties: quarkus.http.port=8080 - Dockerfile: EXPOSE 8080, HEALTHCHECK on port 8080 - .lionsctl.yaml: port 8080 in all configurations This fixes the pod restart loop caused by liveness/readiness probes checking port 8080 while the app was listening on port 8086.
25 lines
407 B
YAML
25 lines
407 B
YAML
# Configuration lionsctl pour unionflow-client
|
|
deployment:
|
|
replicas: 1
|
|
domain: unionflow.lions.dev
|
|
port: 8080
|
|
environment: production
|
|
|
|
resources:
|
|
limits:
|
|
cpu: "1"
|
|
memory: "1Gi"
|
|
requests:
|
|
cpu: "200m"
|
|
memory: "512Mi"
|
|
|
|
health:
|
|
liveness:
|
|
initialDelaySeconds: 120
|
|
periodSeconds: 10
|
|
port: 8080
|
|
readiness:
|
|
initialDelaySeconds: 60
|
|
periodSeconds: 5
|
|
port: 8080
|