Skip to content

Conversation

@scaps1
Copy link
Contributor

@scaps1 scaps1 commented Dec 16, 2025

Description

Move events exporter to our repo

Why do we need it, and what problem does it solve?

Why do we need it in the patch release (if we do)?

Not necessarily

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: extended-monitoring
type: chore
summary: Move events exporter to our repo
impact_level: default

Signed-off-by: alexey.komyakov <alexey.komyakov@flant.com>
@scaps1 scaps1 added this to the v1.75.0 milestone Dec 16, 2025
@scaps1 scaps1 self-assigned this Dec 16, 2025
@github-actions github-actions bot added the area/monitoring Pull requests that update monitoring modules label Dec 16, 2025
Signed-off-by: alexey.komyakov <alexey.komyakov@flant.com>
@scaps1 scaps1 added the e2e/run/yandex-cloud Run e2e tests in Yandex Cloud label Dec 18, 2025
@deckhouse-BOaTswain
Copy link
Collaborator

deckhouse-BOaTswain commented Dec 18, 2025

🟢 e2e: Yandex.Cloud for deckhouse:move_events_exporter succeeded in 44m17s.

Workflow details

Yandex.Cloud-WithoutNAT-Containerd-1.32 - Connection string: ssh redos@51.250.92.28

🟢 e2e: Yandex.Cloud, Containerd, Kubernetes 1.32 succeeded in 43m7s.

@github-actions github-actions bot removed the e2e/run/yandex-cloud Run e2e tests in Yandex Cloud label Dec 18, 2025
@scaps1 scaps1 marked this pull request as ready for review December 18, 2025 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/monitoring Pull requests that update monitoring modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants