(discussion): k8s-infra chart improvements

[srikanthccv]

1. rename the k8s-infra to agent? - the name of the chart is misleading as it conveys the infra explicit in it, but the same chart can be used to do various other kinds of tasks, such as enriching the trace data emitted by the application in a pod with the k8s information. There are several other things users could perform with this chart
2. ability to easily customise the chart - how does one add a new scrape job without altering the existing jobs? Or, speaking more generally, how does one make partial config changes to the agent without copying the whole chart?
3. should the chart enable & collect everything one can get from the existing available receivers? The one thing people usually expect is that they run an agent in their cluster or environment and expect everything to show up in the UI. This has the downside of collecting unnecessary data, but the upside charm of "it just works" is the best user experience. We can probably take the middle ground of collecting immediately helpful information and giving users an option to enable the rest of the things.

cc @SigNoz/backend @SigNoz/devops

[Nageshbansal]

• The chart has already been marketed as k8s-infra and is referenced in our documentation. While we agree that a more intuitive name like agent might have been better initially, we’ve already committed to the current naming.

• We’ve added support for full customization of the chart, allowing users to make partial configuration changes (e.g., adding new scrape jobs) without needing to copy or overwrite the entire configuration.

• We’ve introduced sensible presets that collect just enough data to populate the SigNoz product effectively. Users can easily enable additional receivers if they want to capture more telemetry.