Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Support for hostAliases #840

Closed
jcon321 opened this issue Oct 14, 2020 · 2 comments · Fixed by #970
Closed

Support for hostAliases #840

jcon321 opened this issue Oct 14, 2020 · 2 comments · Fixed by #970
Labels

Comments

@jcon321
Copy link

jcon321 commented Oct 14, 2020

Hello,

My output has ssl => true, a certificate, and a host with an IP address. The host gave me a self-signed cert with a peer name such as 'elastic-server'.

I would rather not use ssl_certificate_verfication => false. Is it possible to get an update to values.yaml to add hostAliases? Is there a way to modify hostAliases without modifying the helm chart?

Thanks

@jcon321
Copy link
Author

jcon321 commented Oct 14, 2020

for what it's worth, adding this to statefulset.yaml worked...

      hostAliases:
      - ip: 11.22.33.44
        hostnames:
        - "foo.bar"

I know it doesnt pull in from values.yaml and it's bit of a hack, but just showing that it's possible.

# Kubernetes-managed hosts file.
127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
fe00::0 ip6-mcastprefix
fe00::1 ip6-allnodes
fe00::2 ip6-allrouters
10.42.0.23      logstash-logstash-0

# Entries added by HostAliases.
11.22.33.44     foo.bar

@jmlrt jmlrt added the feature label Nov 4, 2020
@jmlrt
Copy link
Member

jmlrt commented Nov 4, 2020

Hi @jcon321,
Thanks for openning this request.
Adding HostAliases support to Elastic charts could be great. Are you interested in creating a PR for that?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants