Bug: orchestrator fail to start when kubelink is not in running state

[gireesh-naidu]

📜 Description

orchestrator fail to start when kubelink is not in running state

👟 Reproduction steps

orchestrator fail to start when kubelink is not in running state

👍 Expected behavior

orchestrator should start serving irrespective of kubelink health status.

👎 Actual Behavior

orchestrator is stuck in crashloop until kubelink comes to running state

☸ Kubernetes version

microk8s

Cloud provider

azure

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct