This should fix misleading restart of config-reloader which happeend in the past, yet giving us some extra guarantee when readiness url is misconfigured.
Alternative is to again - remove startup check logic and ensure our tests guards against misconfiguration of url in our manifests (or metric/alert on configuration not reloading, but's harder). Since the team was not comfortable with removal of readiness check, let's try something that will help in common case or config-reloader starting faster.
This should fix misleading restart of config-reloader which happeend in the past, yet giving us some extra guarantee when readiness url is misconfigured.
Alternative is to again - remove startup check logic and ensure our tests guards against misconfiguration of url in our manifests (or metric/alert on configuration not reloading, but's harder). Since the team was not comfortable with removal of readiness check, let's try something that will help in common case or config-reloader starting faster.