Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Valkey: Metrics exporter uses wrong environment variables #25923

Closed
gtudan opened this issue May 15, 2024 · 4 comments
Closed

Valkey: Metrics exporter uses wrong environment variables #25923

gtudan opened this issue May 15, 2024 · 4 comments
Assignees
Labels
solved stale 15 days without activity tech-issues The user has a technical issue about an application valkey

Comments

@gtudan
Copy link

gtudan commented May 15, 2024

Name and Version

bitnami/valkey:0.1.2

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Install the chart as usual
  2. make sure to enable authentication for Valkey
  3. enable the metrics exporter

Are you using any custom parameters or values?

valkey:
  metrics:
    enabled: true
  auth:
    enabled: true

What is the expected behavior?

Metrics exporter is able to connect to the redis-master

What do you see instead?

Metrics exporter get authentication errors

Additional information

The exporter is still the original redis-exporter. But the configuration properties have been renamed to VALKEY_*, especially VALKEY_PASSWORD. They should still be REDIS_*

The metrics exporter works if I manually set the property:

  metrics:
    enabled: true
    extraEnvVars:
      - name: REDIS_PASSWORD
        valueFrom:
          secretKeyRef:
            name: redis-secret
            key: REDIS
@gtudan gtudan added the tech-issues The user has a technical issue about an application label May 15, 2024
@github-actions github-actions bot added the triage Triage is needed label May 15, 2024
@github-actions github-actions bot removed the triage Triage is needed label May 15, 2024
@github-actions github-actions bot assigned alemorcuq and unassigned javsalgar May 15, 2024
@carrodher carrodher assigned rafariossaa and unassigned alemorcuq May 15, 2024
@rafariossaa
Copy link
Contributor

Hi @gtudan ,
Thanks for spotting this. As you have found the issue and provided a fix for it, would you like to contribute and send a PR ? We will be glad to review and merge it.

@mkyc
Copy link

mkyc commented May 22, 2024

In nevest 0.2.0 version of helm chart that is no longer required. If there is global.valkey.password value set that is enough and VALKEY_PASSWORD is set and is enough.

Copy link

github-actions bot commented Jun 7, 2024

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jun 7, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved stale 15 days without activity tech-issues The user has a technical issue about an application valkey
Projects
None yet
Development

No branches or pull requests

7 participants