Will "consumption-only" plans will ever be replaced in favor of workload profile 'consumption' plans?

[onionhammer]

I worry about fully moving all of our workload profile + consumption environments over to consumption-only Container App Environments because I can foresee the day when I get the dreaded email saying "Move all your environments over to workload profiles before December 31st".

The reason I want to move from workload profiles over to consumption only plan:

Consumption-based workload profiles network stack is incredibly unstable and Microsoft support is unwilling to acknowledge that. We've had about 5 different app environments all flake out constantly over the past few weeks (after more than a year of stability) for any app (it appears) relying on persistent TCP connectivity. Some of these app simply use out-of-the-box docker images like Apache superset, not custom code, but they need to be restarted pretty much daily due to network hiccups.

So is there a commitment to keep consumption-only plans going? Will there be a divergence in functionality / features over time? I.e. will there be new features announced for 'workload profile only' or will consumption only plans be deprecated?

[onionhammer]

Looks like aspire components are only supported in workload profile environments, so maybe it's already started?