Bug: not able to add env in global configuration

[rupinSec]

📜 Description

We are not able to create an env getting the error message: env already exist but the same env is not there.

We are creating an env with the namespace that already exist but in different cluster.

👟 Reproduction steps

create an global configuration and create an env in different cluster with a existing namespace.

👍 Expected behavior

It should create an env actually

👎 Actual Behavior

It is not able to create an env failing with the error env already exists.

☸ Kubernetes version

1.25

Cloud provider

gcp

🌍 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

AB#7141