[Bug]: Cannot delete Atlas Team until removed from all projects

[pavansokkenagaraj]

Is there an existing issue for this?

• I have searched the existing issues

AKO Version

v2.11.0

Distribution

Kubernetes

Kubernetes Version

v1.32

Current Behavior

When attempting to delete a team that’s currently assigned to any project, shows an error:

{"level":"WARN","time":"2025-11-06T18:50:26.158Z","msg":"team ai-corp-devops is assigned to a project. Remove it from all projects before delete","atlasteam":"ai-corp/ai-corp-devops"}

While this behavior might be intentional, it makes automation and reconciliation flows difficult — for example, if a team CR is marked for deletion in GitOps, the operator or user has to manually unassign it from projects before deletion.

Custom Resources to reproduce the issue

{"level":"WARN","time":"2025-11-06T18:50:26.158Z","msg":"team ai-corp-devops is assigned to a project. Remove it from all projects before delete","atlasteam":"ai-corp/ai-corp-devops"}

Steps To Reproduce

1.	Create a team (e.g., DevOps).
2.	Assign it to a project.
3.	Attempt to delete the team via UI or CR deletion.
4.	Observe the error in operator

Logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[pavansokkenagaraj]

One Custom Resource for the whole teams/ org level resources is very impractical.

This ideally means, there can be only one kubernetes cluster attached to one atlas organization and cannot be shared b/w k8s clusters.

[igor-karpukhin]

Hi @pavansokkenagaraj. This is a normal behaviour of the operator. You created a team and assigned it to a project. In order to delete it, you have to first un-assign this team from all projects this team is assigned to. Then you can remove it normally. I'm not sure what do you mean by saying "One Custom Resource for the whole teams". The AtlasProject resource allows to to assign as many teams as you want. As well as one team can be assigned to multiple AtlasProject resources. I hope this answers your question.

[helderjs]

@pavansokkenagaraj

Thank you for bringing this behavior to our attention and detailing the scenario for us. We recognize this limitation in the reconciliation design of our existing resources. Specifically, Teams are currently reconciled directly alongside their associated Project. While we acknowledge that the current behavior is not ideal, we have made a strategic decision to prioritize the development of our new generation of resources.
Given our focus on accelerating the release of this new, more robust architecture, we do not have immediate plans to implement improvements or fixes to the existing resource reconciliation logic.