-
Notifications
You must be signed in to change notification settings - Fork 1.9k
added loadBalancerIP option to service - Kibana #666
added loadBalancerIP option to service - Kibana #666
Conversation
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? |
💚 CLA has been signed |
I have now signed the CLA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but I think you need to merge master in your branch as there is some already implemented changes in your PR.
Also adding a description in the README like in https://github.com/elastic/helm-charts/blame/master/elasticsearch/README.md#L179 could be great (we should add description for other service.XXX
subvalues for better documentation but that we can do it later in another PR).
jenkins test this please |
cla/check |
…bana added loadBalancerIP option to service - Kibana
As for the README. You do not have the same structure in your README for Kibana. It does not makes sense to copy what was in elasticsearch unless you are going to add all of the services.xxx sub-values to the README. Currently it links to the values.yaml, which has been updated to display how to use loadBalancerIP. I notice it failed the linter in the CI/CD pipeline. What errors came from the linter so I can fix them. |
jenkins test this please |
=> You should have 2 white lines between each function.
I guess that's not directly related to the loadBalancerIP change but to the other changes that appears in your commit. |
Your commit still contains some changes which are not relevant for this PR and were already applied in other PR: Could reset your branch and reapply your changes related to
# reset branch
git reset origin/master --hard
# apply your changes to kibana/templates/service.yaml kibana/tests/kibana_test.py kibana/values.yaml
# ...
# recreate commit
git add kibana/templates/service.yaml kibana/tests/kibana_test.py kibana/values.yaml
git commit -m 'added loadBalancerIP option to service - Kibana '
# push force
git push --force |
7af7e11
to
47b4202
Compare
Alright it should be good to go |
That's really strange, your new commit 444a2cc still contain the changes from other PRs. I'm sorry for this but maybe it would be easier to recreate a new branch from master and a new PR to have only the changes require. I don't see another solution. |
Is it merged in different PR? |
Replaced by #726 |
${CHART}/tests/*.py
Opened to address feature #611