Skip to content

Enforcing creation of Prometheus Operator to expose metrics #2426

Open
@talayalon

Description

@talayalon

/kind bug

What happened?
In order to enable the export of the controller metrics, there is a requirement to create install Prometheus Operator, which isn't coming by default with the AWS EKS EBS Add On

What you expected to happen?
The Controller will expose metrics by default when adding the configuration of ".controller.enableMetrics = true".

How to reproduce it (as minimally and precisely as possible)?

  1. Install an EKS
  2. Add to the advanced configuration the following code:
{
  "controller": {
     "enableMetrics": true
   }
}

Anything else we need to know?:
Enabling the export of node metrics works without the need of Prometheus Operator:

{
  "node": {
     "enableMetrics": true
   }
}

Environment

  • Kubernetes version (use kubectl version):
    Client Version: v1.32.0
    Kustomize Version: v5.5.0
    Server Version: v1.30.10-eks-bc803b4
  • Driver version: v1.40.0-eksbuild.1

I would hope that one of the 2 things will happen:

  1. Removal of the required Prometheus Operator from the dependency of enabling controller metrics.
  2. Adding the Prometheus Operator as a helm chart dependency when doing .controller.enableMetrics: true

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions