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

chore: update ksm to v2.12.0 #41051

Merged
merged 3 commits into from
Oct 8, 2024
Merged

chore: update ksm to v2.12.0 #41051

merged 3 commits into from
Oct 8, 2024

Conversation

mauri870
Copy link
Member

@mauri870 mauri870 commented Sep 30, 2024

Proposed commit message

We have test files for ksm v2.12.0 but the module manifest still requires v2.7.0. We need at least v2.11.0 for k8s v1.28.0 according to the versioning matrix.

See https://github.com/elastic/beats/blob/main/metricbeat/module/kubernetes/_meta/test/KSM/ksm.v2.12.0.plain.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related Issues

We have test files for ksm v2.12.0 but the module manifest still requires
v2.7.0.
@mauri870 mauri870 added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Sep 30, 2024
@mauri870 mauri870 self-assigned this Sep 30, 2024
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Sep 30, 2024
@mauri870 mauri870 marked this pull request as ready for review September 30, 2024 18:23
@mauri870 mauri870 requested a review from a team as a code owner September 30, 2024 18:23
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

Copy link
Contributor

mergify bot commented Sep 30, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Sep 30, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 30, 2024
@pierrehilbert pierrehilbert added Team:Cloud-Monitoring Label for the Cloud Monitoring team Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team and removed Team:Cloud-Monitoring Label for the Cloud Monitoring team labels Oct 1, 2024
@mauri870 mauri870 merged commit 6339a42 into elastic:main Oct 8, 2024
37 checks passed
mergify bot pushed a commit that referenced this pull request Oct 8, 2024
We have test files for ksm v2.12.0 but the module manifest still requires
v2.7.0.

(cherry picked from commit 6339a42)
mauri870 added a commit that referenced this pull request Oct 9, 2024
We have test files for ksm v2.12.0 but the module manifest still requires
v2.7.0.

(cherry picked from commit 6339a42)

Co-authored-by: Mauri de Souza Meneguzzo <mauri870@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants