Customize health syncing status via query parameter

[jmcruz1983]

Customize health check status when node is syncing

• use query parameter to override default syncing status
• return default status if wrong parameter passed

Documentation

Health check syncing status can be overridden with custom value passed via query parameter syncing_status.
Therefore, it would be compatible with kubernetes standard health check where 200-399 statuses are considered healthy.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

[CLAassistant]

All committers have signed the CLA.

[rolfyone]

LGTM.
If this is a helpful change more generally, could potentially look at making a spec change on eth2.0-apis so that it's part of the standard api...

[rolfyone]

@jmcruz1983 could you take a look at the CLA for me? thanks...

[jmcruz1983]

FYI @rolfyone
I did sign the CLA,
but don't know why still shows unsigned.

[ajsutton]

I did sign the CLA,
but don't know why still shows unsigned.

Yeah it has approved your GitHub user but doesn't seem to be able to map the commits to that user. From the comment it left above:

Juan Dominguez seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

[ajsutton]

May need to edit the commit so it has an email address with it (can just be the one GitHub generates rather than your real one) and do a force push to replace the commit.

[jmcruz1983]

Thanks @ajsutton
I managed to get it right,
seems that commit was using my GitLab user instead of GitHub.
Now CLA is signed :)