-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[elasticsearch] Run as 1000 #171
[elasticsearch] Run as 1000 #171
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? |
bceb0f3
to
74d5b82
Compare
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.
jenkins test this please |
3c76657
to
6af3ab2
Compare
e9b47cb
to
08e6eee
Compare
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.
Couple small tweaks and then this one is ready to be merged too!
08e6eee
to
2c05750
Compare
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!
jenkins test this please |
CI failure is coming from the linting test:
|
2c05750
to
9340b44
Compare
Signed-off-by: Naseem <naseemkullah@gmail.com>
9340b44
to
42c88fa
Compare
jenkins test this please |
Seems like Jenkins nodes are offline? :)
|
This is expected, a fresh VM is spun up for every build and is set offline so that it can't be re-used. The build failed because creating the test GKE cluster failed. jenkins test this please |
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! Thanks a lot for working on getting this in and tested!
Template tests for the changes from #171
My pleasure! |
Template tests for the changes from #171
Template tests for the changes from #171
Template tests for the changes from #171
Template tests for the changes from #171
${CHART}/tests/*.py
${CHART}/examples/*/test/goss.yaml