Not specifying atlasTeams in project spec removes pre existing teams from project

[RafaelBroseghini]

What did you do to encounter the bug?
Applying a project with teams managed outside of k8s and empty project.spec.teams unassigns all teams from project.

What did you expect?
I would expect the operator to only manage the teams it has knowledge of, perhaps via status.

What happened instead?
All teams managed outside k8s get unassigned from project.

Operator Information

• 2.8.0

Additional context
I will give more context on the underlying issue: User invitation + invitation acceptance detection + team assignment cannot be managed via the operator, so we're looking at potentially a different way of managing that flow, which leads to trying to manage atlas team outside the operator.

The project controller tries to reconcile all team assignments vs the project spec when in my opinion it should try to reconcile against what the project object knowledge of, perhaps via status. This is where it detects what to delete:

mongodb-atlas-kubernetes/internal/controller/atlasproject/teams.go

Lines 91 to 95 in 8b30aee

	desiredTeam, ok := teamsToAssign[atlasAssignedTeam.TeamID]
	if !ok {
	toDelete = append(toDelete, &atlasAssignedTeam)
	continue
	}

[roothorp]

Hi @RafaelBroseghini, thanks for the issue and the details! We are looking into this and will respond here as soon as we have more info.