fix support wildcard tls host on ingress

[diegofernandes]

• Chart version not bumped (the versions are all bumped and released at the same time)
• README.md updated with any new values or changes
• Updated template tests in ${CHART}/tests/*.py
• Updated integration tests in ${CHART}/examples/*/test/goss.yaml

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[Crazybus]

LGTM! Nice find! It seems like the value just needed to be quoted properly, however I think your approach is much much cleaner.

FYI this is what comes from the helm create template so its very possible that this needs to be fixed upstream too in the helm repo.

[Crazybus]

jenkins test this please

[diegofernandes]

@Crazybus I had tried quoted my config, but It's cause an error.

Error: YAML parse error on kibana/templates/ingress.yaml: error converting YAML to JSON: yaml: line 16: did not find expected alphabetic or numeric character
Error: UPGRADE FAILED: YAML parse error on kibana/templates/ingress.yaml: error converting YAML to JSON: yaml: line 16: did not find expected alphabetic or numeric character

[Crazybus]

Thank you again for finding and fixing this!

@Crazybus I had tried quoted my config, but It's cause an error.

Yeah in the config didn't work, I meant quoting it inside the template. Your solution is much cleaner though 👍