Unable to build kubernetes objects from release manifest

[Mythic4l]

I followed the EKS method of installation step by step yet I faced this issue :

Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "prometheus-rds-exporter-prometheus-rds-exporter-chart" namespace: "" from "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"

after excurting the command:
prometheus-rds-exporter \ oci://public.ecr.aws/qonto/prometheus-rds-exporter-chart \ --version ${PROMETHEUS_RDS_EXPORTER_VERSION} \ --install \ --namespace ${KUBERNETES_NAMESPACE} \ --set serviceAccount.annotations."eks\.amazonaws\.com\/role-arn"="${SERVICE_ACCOUNT_ANNOTATION}" \ --set serviceAccount.name="${IAM_ROLE_NAME}"

[qfritz]

Hi, this looks similar to #229

Is there a Prometheus Operator deployed in your cluster?

If no, please try installing it first and retry RDS exporter deployment 🙇‍♀️

[Mythic4l]

I only installed the CRD from prometheus operator and also i needed to do some changes on the service account created as it was showing this error:

Error: Unable to continue with install: ServiceAccount "prometheus-rds-exporter" in namespace "monitoring" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: key "app.kubernetes.io/managed-by" must equal "Helm": current value is "eksctl"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "prometheus-rds-exporter"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "monitoring"

BTW i have prom deplyed using a normal helm, will this create any malfunction for the prom or the rds exporter

[warchief-t]

@Mythic4l
You created EKS service account without Helm.
So, delete your EKS service account and create it with Helm.

And please be sure that the value from --set serviceAccount.name="SA_NAME" equals the one mentioned in your IAM role "oidc.eks.region-code.amazonaws.com/id/EXAMPLED539D4633E53DE1B71EXAMPLE:sub" = "system:serviceaccount:NAMESPACE:SA_NAME" as described here: https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html