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
Describe the bug
Unable to process requests when deploying with nginx sidecar container
I am unsure if this is a bug or misconfiguration from my side.
From the docs
Docker version and underlying OS
To Reproduce
Steps to reproduce the behavior:
extraContainers: #[]
- name: nginx-proxy-sidecar
image: nginx:latest
ports:
- name: http-nginx
containerPort: 80
protocol: TCP
volumeMounts:
- name: nginx-config
mountPath: /etc/nginx/nginx.conf
subPath: nginx.conf # Mount the nginx.conf file from the ConfigMap
readOnly: true
# extraVolumes -- Define extra Volumes. Allow to add existing claimName
extraVolumes: #[]
- name: nginx-config
configMap:
name: nginx-config-volume # The name of the ConfigMap created manually
service:
# service.type -- Type of Kubernetes service to create
type: ClusterIP
# service.port -- Port for the Kubernetes service to expose
port: 80 # 80 for nginx-sidecar | 9011 - original for application
# service.annotations -- Extra annotations to add to service object
targetPort: http-nginx
annotations: {}
# service.spec -- Any extra fields to add to the service object spec
spec: {}
Expected behavior
I am expecting nginx container will be processing requests
targetPort - respected and applied in configuration
Describe the bug
Unable to process requests when deploying with nginx sidecar container
I am unsure if this is a bug or misconfiguration from my side.
From the docs
Docker version and underlying OS
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I am expecting nginx container will be processing requests
targetPort - respected and applied in configuration
I have a workaround that by locally modifying
charts/chart/templates/ingress.yaml
Line 50 in a2f97bb
and
https://github.com/FusionAuth/charts/blob/a2f97bb90d5a55db761a3e9a3a2644bedd88a6ec/chart/templates/service.yaml#L16C1-L20C17
The text was updated successfully, but these errors were encountered: