Problem

The registry-rest-api-tests workflow (pr-rest-API-tests) is structurally flaky. When it fails, all 28 tests fail with the same error:
assert 502 == 200
This happens across multiple branches (master, fix_complex_type, dependabot/*, etc.) and is not caused by any specific code change.

Suspected Root Cause

The test fixture checks two conditions before starting tests:

1. Pod status → Running
2. FeatureStore CR status → Ready

However, the HTTP endpoint behind the ingress may not be ready to serve traffic even when Pod/CR are Ready. Tests start immediately, hitting the ingress before the backend is fully initialized, resulting in 502 Bad Gateway responses.

Possible Solution

add an HTTP readiness poll to the test fixture in sdk/python/tests/integration/registration/rest_api/test_registry_rest_api.py. After confirming Pod/CR readiness, poll the actual HTTP endpoint until it returns 200 before starting tests: