fix(api): block device WaitForUserUpload phase

[hardcoretime]

Description

• Added a GET method to the upload URL to signal that the upload server is ready to serve.
• Added a readiness probe to the uploader pod.
• Fixed missing output from the data export in the E2E test case.
• Fixed the WaitForUserUpload phase for block devices.

Why do we need it, and what problem does it solve?

The WaitForUserUpload phase for block devices was being set incorrectly because the ingress controller requires some time to apply the configuration from the uploader ingress resource. This delay can cause 503 and 413 status codes on upload operations if they start before the ingress configuration is applied.

What is the expected result?

• The uploader pod is ready when the readiness probe is successful.
• The WaitForUserUpload phase is set when the uploader server returns an HTTP status OK.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: api
type: fix
summary: "Enhanced reliability of the upload server for block devices by adding readiness checks and fixing configuration delays to prevent upload errors."

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.