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

Bump grafana image #3445

Draft
wants to merge 1 commit into
base: dev-v2.9
Choose a base branch
from
Draft

Conversation

joshmeranda
Copy link
Contributor

Issue:

Problem

Solution

Monitoring uses an older version of the grafana image than we should be (9.1.5 instead of 10.1.0)

Testing

Engineering Testing

Manual Testing

Monitoring still works as expected and metrics flow and are displayed as expected.

Automated Testing

QA Testing Considerations

Regressions Considerations

Backporting considerations

Should backport to 2.8

Copy link

github-actions bot commented Feb 8, 2024

Validation steps

  • Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.
  Ex:- 
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  
  • Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
  • Approve the PR to run the CI check.

@recena recena marked this pull request as draft February 14, 2024 17:59
@recena recena changed the title [WIP] bump grafana image Bump grafana image Feb 14, 2024
@recena
Copy link
Collaborator

recena commented Feb 14, 2024

@joshmeranda We are using this GH feature to avoid notifications when the PR is not ready yet.

@Skoucail
Copy link

Skoucail commented Apr 25, 2024

Any update on this?
I tried updating grafana to 10.3.3 with the helm chart values.yaml (latest available rancher/mirrored-grafana-grafana image) but the integraton with rancher all broke.

(Version 9.1.5 has atleast 2 known vulnerabilities, so keeping it more up-to-date seems like a must in this time and age)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants