Terraform destroy failed

[jrDevBot]

Summary

After an unsuccessful trial at setting up JenkinsX on EKS. It created 3 m5.large instances running. I am trying to destroy whatever resources were created so that I don't incur additional charges.

Steps to reproduce the behavior

Expected behavior

removal of all the resources

Actual behavior

╷
│ Error: Get "http://localhost/api/v1/namespaces/kube-system/configmaps/aws-auth": dial tcp 127.0.0.1:80: connect: connection refused
│ 
│   with module.eks-jx.module.cluster.module.eks.kubernetes_config_map.aws_auth[0],
│   on .terraform/modules/eks-jx.cluster.eks/aws_auth.tf line 63, in resource "kubernetes_config_map" "aws_auth":
│   63: resource "kubernetes_config_map" "aws_auth" {
│ 
╵
╷
│ Error: Kubernetes cluster unreachable: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
│ 
│   with module.eks-jx.module.vault.helm_release.vault-operator[0],
│   on .terraform/modules/eks-jx/modules/vault/charts.tf line 1, in resource "helm_release" "vault-operator":
│    1: resource "helm_release" "vault-operator" {

Terraform version

The output of terraform version is:

$ terraform version
Terraform v1.4.0
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v4.58.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.3.2
+ provider registry.terraform.io/hashicorp/helm v2.9.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.18.1
+ provider registry.terraform.io/hashicorp/local v2.4.0
+ provider registry.terraform.io/hashicorp/null v3.2.1
+ provider registry.terraform.io/hashicorp/random v3.4.3
+ provider registry.terraform.io/hashicorp/template v2.2.0
+ provider registry.terraform.io/terraform-aws-modules/http v2.4.1

Module version

Operating system

Ubuntu 22