-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Fix serviceAccount for APM server #786
Fix serviceAccount for APM server #786
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 |
cla/check |
Hi @caiconkhicon, |
@jmlrt : Yes I did that, I also downloaded the PDF, the UI shows:
What else do I need to do? |
cla/check |
Can you confirm that you signed the CLA with the same email that you used in your commit? |
2d81d1a
to
6f2a821
Compare
cla/check |
6f2a821
to
b382a18
Compare
jenkins test this please |
@jmlrt : I guess it works now? |
@caiconkhicon Can you merge master on your branch? |
Sorry I don't get what you mean. You mean rebase master on my branch? I can do it now. |
---- - In the current Helm chart for `apm-server`, serviceAccount for the Deployment is only set when `serviceAccount` is set in `values.yaml`. However, it is wrong. `serviceAccount` should always be set because even when no `serviceAccount` is set in `values.yaml`, a managed one is still created. What ---- - Always set `serviceAccount` for apm-server Deployment to the template apm.serviceAccount defined in `_helpers.tpl`
b382a18
to
8b6a904
Compare
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⛴
backported to |
Why
apm-server
, serviceAccount for theDeployment is only set when
serviceAccount
is set invalues.yaml
.However, it is wrong.
serviceAccount
should always be set because evenwhen no
serviceAccount
is set invalues.yaml
, a managed one is stillcreated.
What
Always set
serviceAccount
for apm-server Deployment to the templateapm.serviceAccount defined in
_helpers.tpl
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