[bitnami/wildfly] misconfigured mgmtIngress annotations

[emilianosantucci]

Name and Version

bitnami/wildfly 15.2.1

What architecture are you using?

arm64

What steps will reproduce the bug?

1. helm install wildfly bitnami/wildfly --version 15.2.1 -f values.yaml

Are you using any custom parameters or values?

exposeManagementConsole: true
ingress:
  enabled: true
  hostname: wildfly.192.168.70.2.nip.io
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 10m
mgmtIngress:
  enabled: true
  hostname: wildfly-management.192.168.70.2.nip.io
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 100m

What is the expected behavior?

• ingress accept upload with max size 10m
• mgmtIngress accept upload with max size 100m

What do you see instead?

Created ingress not inherit annotations added to values.yaml.

Additional information

Workaround used:

Use commonAnnotations into values.yaml as below:

commonAnnotations:
  nginx.ingress.kubernetes.io/proxy-body-size: 100m

I know it is not the best choice (it set this annotations on all components created) but allow me to load WAR with a size greater than 1Mb.

Hint for the resolutions:

I'm not a Helm master but I think the issue is on this template at row 19:

• Is:

    {{- $annotations := include "common.tplvalues.merge" ( dict "values" ( list .Values.persistence.annotations .Values.commonAnnotations ) "context" . ) }}

• Should be:

    {{- $annotations := include "common.tplvalues.merge" ( dict "values" ( list .Values.mgmtIngress.annotations .Values.commonAnnotations ) "context" . ) }}

[javsalgar]

Hi!

Thank you so much for spotting it! Indeed, the issue is exactly as you mentioned. As you discovered it, would you like to submit a PR changing that line of the ingress file?

[emilianosantucci]

Hi @javsalgar,
thank you for the feedback, I just open a PR for the fix.

Please feel free to give any advice about it.