0xbitmonk
(Pranav Prakash)
October 22, 2024, 7:40am
1
When I delete my cluster ( I have already deleted environment and all apps/dbs associated), I get this error in screenshot.
Cluster ID: 2b22b057-02fa-4dcc-b032-3f53b6cb0256
Exec ID: eb1bbbda-e17e-4bc4-9180-c9937a90c9d0-1729580848
Org Id: 0f2a7baf-84e9-4b4e-a219-72fb44811f99
How can I get rid of this cluster?
ce_gagnaire
(Charles-Edouard Gagnaire)
October 23, 2024, 1:10pm
2
Hello @0xbitmonk ,
I’ll check with the team to confirm the problem.
I’ll get back to you.
Regards,
Charles-Edouard
0xbitmonk
(Pranav Prakash)
October 23, 2024, 5:01pm
3
Cluster ID: 2757a5b0-bc65-4a87-b1ef-076047c99b59
Exec Id: 36a808f5-94f8-42bf-b74a-31df050fddaa-1729694769
Org ID: 0f2a7baf-84e9-4b4e-a219-72fb44811f99
This happened with another of my cluster. If it helps your team, we had a managed Postgres DB which was unable to be deleted via Qovery, so we deleted it via AWS Console itself.
bchastanier
(Benjamin Chastanier)
October 24, 2024, 7:58am
4
Hello @0xbitmonk ,
You’ve got this error because you have some entities / resources not managed by Qovery attached to the policy we are trying to delete.
You can find those by using the following AWS cli command:
aws iam list-entities-for-policy \
--policy-arn arn:aws:iam::020942130480:policy/qovery-aws-iam-eks-user-mapper-z2757a5b0
It returns the following:
So I guess, you need to delete this user policy mapping and trigger deletion again.
Cheers,