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

[kibana] Explicitly set the targetPort to the defined http port #134

Merged
merged 1 commit into from
May 21, 2019

Conversation

Crazybus
Copy link
Contributor

@Crazybus Crazybus commented May 15, 2019

Fixes #133

Before this it wasn't possible to change the service port to anything
other than 5601. E.g. if the service.port was changed to 80 then the
targetPort would also be set to 80 even though Kibana was listening on
5601.

  • 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 #133

Before this it wasn't possible to change the service port to anything
other than 5601. E.g. if the `service.port` was changed to `80` then the
targetPort would also be set to 80 even though Kibana was listening on
5601.
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.

Good catch 🚢

@Crazybus Crazybus merged commit 89907bf into master May 21, 2019
@Crazybus Crazybus deleted the glass_o_port branch May 21, 2019 08:59
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.

No targetPort in kibana deployment
2 participants