Skip to content

feat: Add FleetControl metadata and automated release workflow for agent-control integration - logging#2162

Merged
jcoscollanr merged 5 commits into
masterfrom
feat/integrate-with-newrelic-control-metadata-logging
May 8, 2026
Merged

feat: Add FleetControl metadata and automated release workflow for agent-control integration - logging#2162
jcoscollanr merged 5 commits into
masterfrom
feat/integrate-with-newrelic-control-metadata-logging

Conversation

@jcoscollanr
Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

This PR integrates the helm charts with New Relic's agent metadata service (agent-control) to enable centralised fleet management and automated version tracking. It adds:

Which issue this PR fixes

Enables integration with New Relic's agent-control platform for centralised fleet management.

Special notes for your reviewer:

  • The workflow uses a matrix strategy to handle multiple charts (nr-ebpf-agent, nri-bundle, nr-k8s-otel-collector, newrelic-logging, pipeline-control-gateway)
  • Only charts with existing .fleetControl directories will trigger metadata uploads

Checklist

  • Chart Version bumped
  • Variables are documented in the README.md
  • Title of the PR starts with chart name or describes multi-chart changes

@jcoscollanr jcoscollanr self-assigned this Mar 16, 2026
@jcoscollanr jcoscollanr requested a review from a team as a code owner March 16, 2026 09:36
@@ -0,0 +1,5 @@
agentControlDefinitions:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we have an approach so that we don't make any changes here in logging helm chart, instead it can be centralized from the agent control side?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Having a centralized approach doesn't scale well, there are dozens of agents in NR.

Keeping the agent configuration in each agent's own repository is intentional. It ties the config lifecycle directly to the agent's release flow. If the agent changes (e.g. a new required parameter), the config change ships in the same PR

namespace: newrelic
name: io.fluentbit
version: 0.1.0
variables:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is there any impact on new logging chart?

type: yaml
required: false
default: null
deployment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

can you add tests?

@jcoscollanr jcoscollanr merged commit 0a567a6 into master May 8, 2026
12 checks passed
@jcoscollanr jcoscollanr deleted the feat/integrate-with-newrelic-control-metadata-logging branch May 8, 2026 10:32
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