[fluentd-elasticsearch] Wrong port exposed when awsSigning sidecar is running

[Alien2150]

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes:

helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}

Which chart in which version:

What happened:
The wrong port (PORT_NUM) is used on the chart file when enabling awsSigningSidecar. It should not use the "Values.elasticsearch.port" but the used port it creates the opening connection.

What you expected to happen:
Expose the used hardcoded port. In this case: 8080

How to reproduce it (as minimally and precisely as possible):

• Set awsSigningSidecar.enabled to true.
• Install the helm chart
• Verify the wrong exposed port:

k exec -n kube-system fluentd-.... -c fluentd-elasticsearch-aws-es-proxy  printenv  | grep PORT_NUM

Anything else we need to know: