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

[kibana] Always set server.host to the docker default #168

Merged
merged 1 commit into from
Jun 18, 2019
Merged

Conversation

Crazybus
Copy link
Contributor

@Crazybus Crazybus commented Jun 17, 2019

Fixes: #156

The Kibana docker image comes with
server.host
set in the default kibana.yml. This setting is needed to make sure
that services and ingress work correctly. If someone overrides the
kibana.yml with custom configuration this setting changes back to the
kibana default which is localhost.

This keeps the setting consistent for the default helm install with
default values and for anyone customising kibana.yml

  • 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

Fixes: #156

The Kibana docker image comes with
[server.host](https://github.com/elastic/kibana/blob/3a1d4ad0acd986f55b7da532878e842dd62a1237/src/dev/build/tasks/os_packages/docker_generator/templates/kibana_yml.template.js#L30)
set in the default `kibana.yml`. This setting is needed to make sure
that services and ingress work correctly. If someone overrides the
kibana.yml with custom configuration this setting changes back to the
kibana default which is `localhost`.

This keeps the setting consistent for the default helm install with
default values and for anyone customising `kibana.yml`
@Crazybus Crazybus requested a review from tylerjl June 17, 2019 17:57
Copy link
Contributor

@tylerjl tylerjl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a tricky one, agreed with the default value to ensure it's consistent 👍

@Crazybus Crazybus merged commit e6771f4 into master Jun 18, 2019
@Crazybus Crazybus deleted the bounded_host branch June 18, 2019 07:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

502 error when accessing ingress
2 participants