You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We see than when we install with NIGINX everything is working fine but then changing to ingress GCE with below annotations its creating 2 services one is healthy and other is unhealthy.
apiVersion: v1
kind: Service
metadata:
name: {{ .Values.container.name }}
labels:
{{ include "app.labels" . | indent 4 }}
spec:
# This is needed so that DNS resolves between containers in a statefulset
# before they are marked "Ready", as containers are only marked "Ready" after
# they are running. Our containers need to talk to each other during start-up.
publishNotReadyAddresses: true
clusterIP: None
ports:
- name: http
port: {{ .Values.app.port | default 8080 }}
targetPort: 8080
{{- if .Values.app.portRange }}
{{- $ports := split "-" .Values.app.portRange -}}
{{- range untilStep ($ports._0|int) ($ports._1|int) 1 }}
- name: tcp-{{ . }}
port: {{ . }}
protocol: TCP
targetPort: {{ . }}
{{- end }}
{{- end }}
selector:
app: {{ template "app.name" . }}
The text was updated successfully, but these errors were encountered:
We see than when we install with NIGINX everything is working fine but then changing to ingress GCE with below annotations its creating 2 services one is healthy and other is unhealthy.
below are the services which are being created
by default the health check is checking on HTTP 80 and when i change it to TCP 3128 its becoming healthy and i was able to access the ingress URL.
i dont know from which service readiness probe i am getting the healthcheck created as below i didnt mention anywhere HTTP 80
Squid-svc.yaml
app-ingress.yaml
squid.yaml
app-service.yml
The text was updated successfully, but these errors were encountered: