Path to 2.0

[petewall]

Hey k8s-monitoring Community!

I wanted to offer a sneak peek into what's being planned for the next major release of the Helm chart, version 2.0.

In true major release fashion, this will include several breaking changes, but I truly hope that it'll be worth the upgrade pain.

What's being added

• Ability to specify multiple destinations for the same data types
  Want to send metrics to a local Prometheus and to a SaaS hosted metrics service, like Grafana Cloud? Yeah, it'll do that.

• Ability to add service integrations (i.e. scrape common services, databases, etc...) without needed to copy/paste into extraConfig

• Better OTLP pipeline support and features

• More intelligent ways of using Alloy instances and distributing the work across them

What's changing

Nearly all of the existing values.yaml will need to be migrated. I will create a migration utility to help.

What's not changing

As best as I can, none of the existing functionality will be lost. It may be renamed, but there should be an equivalent way of doing things.

I've been blown away by the support, contributions, engagement, and feedback you all have given. I intend to honor that and release a new version that'll be worth the wait. It's too early to provide a timeline, but I am actively working on it now.

[petewall]

All this being said, I will be marking issues and PRs with the 2.0 milestone for things that will be addressed in the major release.