Workflow fails with 'resource type not found' error after Radius install — UCP pod readiness missing

[brooke-hamilton]

Bug information

Steps to reproduce (required)

1. Run the workflow: example job failure
2. This job attempts to deploy ./tests/test-local-dev-recipes.bicep after installing Radius on a local k3d cluster.

Observed behavior (required)

The workflow fails after installing Radius, with the following error:

Error: {
  "code": "BadRequest",
  "message": "resource type \"Microsoft.Resources/deployments\" not found",
}
TraceId:  6cc2f4a0cbce526ebbe972827112f8af
##[error]Process completed with exit code 1.

It appears the job attempts resource deployment before ensuring the UCP pod is ready. No explicit readiness check for the UCP pod is present prior to deploy.

Desired behavior (required)

The workflow should wait for the UCP pod to be ready after Radius is installed, before attempting to deploy any resources. This can improve reliability and prevent resource type not found errors.

Workaround (optional)

No known workaround yet.

System information

rad Version (required)

Operating system (required)

Additional context

• Workflow job example: actions run job
• Full workflow: test.yaml
• It appears there is no step to explicitly wait for the UCP pod after Radius install, before resource deployment.