Skip to content

Add the ability to set server and enforcement parameters #1777

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

Merged
merged 3 commits into from
Jul 17, 2025

Conversation

petewall
Copy link
Collaborator

No description provided.

@petewall petewall requested a review from rlankfo as a code owner July 17, 2025 18:30
@petewall petewall self-assigned this Jul 17, 2025
@petewall petewall requested a review from Copilot July 17, 2025 18:30
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces configuration options for gRPC server parameters and keepalive enforcement in the OTLP receiver, exposing them via Helm values, JSON schema, templates, and documentation.

  • Added server_parameters and enforcement_policy in rendered outputs for tests and examples
  • Extended values.yaml and values.schema.json to support serverParameters and enforcementPolicy
  • Updated the OTLP Helm template and README to render and document the new settings

Reviewed Changes

Copilot reviewed 28 out of 28 changed files in this pull request and generated no comments.

Show a summary per file
File Description
charts/k8s-monitoring//tests//*/.rendered/output.yaml Added server_parameters and enforcement_policy blocks to test outputs
charts/k8s-monitoring/docs/examples/**/{output.yaml,alloy-receiver.alloy} Included new parameters in all example configurations
charts/k8s-monitoring/charts/feature-application-observability/values.yaml Introduced serverParameters and enforcementPolicy fields
charts/k8s-monitoring/charts/feature-application-observability/values.schema.json Extended schema to validate the new fields
charts/k8s-monitoring/charts/feature-application-observability/templates/_receiver_otlp.tpl Template logic added to render the new parameters
charts/k8s-monitoring/charts/feature-application-observability/README.md Documented defaults and descriptions for the new parameters

Copy link

@dehaansa dehaansa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Only thought is a question, whether you want the default values to be written literally vs allowing the defaults in Alloy/OTel to take affect when no values are given. I'm not sure what the standard patterns are for that in the k8s-monitoring chart.

@petewall
Copy link
Collaborator Author

Updated to fix the issues as well as use alloy's defaults.

@petewall petewall merged commit 75b24f1 into main Jul 17, 2025
52 of 53 checks passed
@petewall petewall deleted the fix/add-max_connection_age branch July 17, 2025 21:04
petewall added a commit that referenced this pull request Jul 17, 2025
* Add the ability to set server and enforcement parameters

Signed-off-by: Pete Wall <[email protected]>

* Fix and refactor to use Alloy's defaults

Signed-off-by: Pete Wall <[email protected]>

* update rendered output

Signed-off-by: Pete Wall <[email protected]>

---------

Signed-off-by: Pete Wall <[email protected]>
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.

2 participants