[fix] Detach velero node policy on cluster deletion (#664)

* [fix] Detach velero node policy on cluster deletion If we won't detach the IAM policy then it's not possible to delete the cluster. Ticket: https://mattermost.atlassian.net/browse/CLD-2450 * Update internal/provisioner/kops_provisioner_cluster.go Co-authored-by: Gabe Jackson <[email protected]> Co-authored-by: Gabe Jackson <[email protected]>
mattermost · Jun 8, 2022 · bb19dd8 · bb19dd8
1 parent a43adbf
commit bb19dd8
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/internal/provisioner/kops_provisioner_cluster.go b/internal/provisioner/kops_provisioner_cluster.go
@@ -954,6 +954,10 @@ func (provisioner *KopsProvisioner) cleanupKopsCluster(cluster *model.Cluster, a
 	if err != nil {
 		return errors.Wrap(err, "unable to detach custom node policy")
 	}
+	err = awsClient.DetachPolicyFromRole(iamRole, aws.VeleroNodePolicyName, logger)
+	if err != nil {
+		return errors.Wrap(err, "unable to detach velero node policy")
+	}
 
 	_, err = kopsClient.GetCluster(kopsMetadata.Name)
 	if err != nil {