Bug: Restart in orchestrator just after release

[prkhrkat]

📜 Description

When cluster namespace is getting updated and fetched concurrently, there is a case of read and write in map, which gives panic.the

👟 Reproduction steps

Rare occurrence, hard to reproduce

👍 Expected behavior

must not panic

👎 Actual Behavior

Restart in orchestrator just after release

☸ Kubernetes version

EKS 1.21

Cloud provider

🌍 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