Skip to content

Add readiness probe to Vector linked to configurator

Niko Belokolodov requested to merge verify-configurator-is-available-for-vector into main

What does this MR do and why?

Closes https://gitlab.com/gitlab-org/analytics-section/product-analytics/analytics-stack/-/issues/74

This MR adds readiness probe to Vector. The probe checks Configurator as an external dependency service and makes sure its available (means migrations finished running) hence Clickhouse schema was updated and ready for accepting new events data

from the docs:

Sometimes, applications are temporarily unable to serve traffic. For example, an application might need to load large data or configuration files during startup, or depend on external services after startup. In such cases, you don't want to kill the application, but you don't want to send it requests either. Kubernetes provides readiness probes to detect and mitigate these situations. A pod with containers reporting that they are not ready does not receive traffic through Kubernetes Services.

%{first_multiline_commit}

MR acceptance checklist

  • The correct type labels have been applied to this MR.
  • This MR has been made as small as possible, to improve review efficiency and code quality.
  • This MR has been self-reviewed per the code review guidelines.
  • The changes have undergone manual testing and are functioning as intended.
  • This MR has updated the Chart.yaml version number following SemVer versioning practices.
  • This MR documents any breaking changes in the MR description, and the upgrade path has been documented in the first commit as well as in MR description.

How to set up and validate

Numbered steps to set up and validate the change are strongly suggested.

How to deploy upon merging

Numbered steps to explain how this change needs to be deployed. For instance, if there are any changes that should be made outside of the code changes themselves.

Edited by Niko Belokolodov

Merge request reports