[BUG] Flyte Propeller does not have readiness/liveness checks

[Sovietaced]

Describe the bug

When deploying a new version of Flyte Propeller it's quite easy for Flyte Propeller to get into a bad state if there is an issue during initialization of Flyte Propeller (either due to an issue with Flyte Propeller binary or the configuration of Flyte Propeller). The reason for this is because there are no readiness/liveness checks to indicate that Flyte Propeller is healthy so Kubernetes will promote the new version of Flyte Propeller as long as the container runs.

I personally encountered this while configuring some of our own plugins.

Expected behavior

Ideally Flyte Propeller should only be marked as ready by Kubernetes once it has completed initialization and hasn't encountered any issues.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• [x] Yes

Have you read the Code of Conduct?

• [x] Yes

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 90 days and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[kumare3]

Keeping this open

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[Sovietaced]

Keeping this open

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"