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 operator from 0.71.2 to 0.80.2 in helm-charts/splunk-otel-collector/Chart.yaml #1678

Merged
merged 3 commits into from
Feb 26, 2025

Conversation

jvoravong
Copy link
Contributor

@jvoravong jvoravong commented Feb 26, 2025

Description:

  • Bumping the operator subchart version. Most of the changes in this PR were auto-generated with CI/CD, only the new test data updates were created by me manually.
  • The functional tests started to fail because the included target allocator started emitting more metrics for our k8s cluster receiver integration. These new metrics are optional and not included with the default deployment of this chart, so I did not mark this change as breaking. Had to update the expected test data in expected_cluster_receiver.yaml content.
  • New metrics for the target allocator include: k8s.container.cpu_limit, k8s.container.cpu_request, k8s.container.memory_limit, k8s.container.memory_request
  • This PR unblocks Use Helm generated instead of cert-manager generated certs for the operator #1648

jvoravong and others added 3 commits February 26, 2025 08:44
@jvoravong jvoravong marked this pull request as ready for review February 26, 2025 16:27
@jvoravong jvoravong requested review from a team as code owners February 26, 2025 16:27
@jvoravong jvoravong merged commit 16dae9c into main Feb 26, 2025
77 checks passed
@jvoravong jvoravong deleted the update-operaetor-jv branch February 26, 2025 18:05
@github-actions github-actions bot locked and limited conversation to collaborators Feb 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants