What apps are you trying to use?

It's bad to force the usage of legacy app if it's not necessary....

I try to use personal applications : timescaledb Cluster, graphite servers and custom prometheus

Having to change everything from one version to the next to run on minor versions when you can have applications in production is not normal. And if the solution is to have to uninstall everything to reinstall everything, it is not possible.

I always pass by rancher to install/upgrade applications

at first part onto the cluster manager interface (2.2, 2.3 and 2.4) and after that I manage them in the new cluster explorer (2.5). I migrate application are not sj=hown in the cluster explorer part. After research they have the managed-by tiller annotation, but the cluster manager used helm v3 to install them. I had no tiller part installed in my cluster at all. I made research to fix them and manage them correctly with helm : change annotations to speak to helm it's him the manager of my resources. I change all resources (statefullset, deployment, ingress, service, pvc, ...) After that, all works fine, the cluster explorer show all my applications and I can manage them directly in that part. It works like a charm. But now, rancher 2.6 block me to do that and want to pass to the legacy part after I migrate all of them : I can't return to the legacy part. If the solution is to remove legacy apps, I can make that but It's possible to remove legacy apps and keep all resources ?

Really disappointed with your solution since 1 year... I should never have trusted you.

Since the new interface, we lost many cool things (possible to easilly switch to oldest application history, known the age of the specific pod, ...)

In terms of 2.6 in general resources can be sorted by the

Age

column and the actual creation time can be seen by hovering over that entry

ok for the v2 to v3 migration, I can understand. But if all is working with helm 3, we can flag the app to say "Do not consider it as legacy app" ?

And I have no difference in applications api definition or yaml to show what it flag it as legacy... I have others migrated legacy apps and I can correctly upgrade them in App & marketplace with no reason...

After research, another peoples are the same problem : https://forums.rancher.com/t/migrate-legacy-apps-catalog-to-apps-marketplace/37252

https://github.com/rancher/rancher/issues/29758 https://github.com/rancher/rancher/issues/36319 https://github.com/rancher/rancher/issues/34853

the problem is rancher here, not helm with the usage of legacy apps or not

I never install tiller in my clusters. I never launch helm install manually (I just made helm list -A to verify the existing of the apps in helm part). And, with no reason, rancher install many correctly and others not and annotate them managed by tiller, But this part is fixed. I fix all of it bu now, the app is correctly shown by Helm, correctly shown in rancher app & marketplace but rancher want to manager them only in legacy part (but for several the app & marketplace part works fine) with no reason and with no link with migrated apps or not

the rancher management between ember and helm 3 is a really mess and really buggy....

So the concern of migration is not from helm, but from rancher itself. You should have made a clean tutorial of application migration. And without going through helm 2to3, it doesn't work at all, especially if you never went through Tiller but rancher says the opposite... Nobody could explain this to me before and now we're stuck with helm 2to3 anyway? Next time, please say in bold that your product is not ready or else remain blocked on old versions because we can find ourselves not managing anything on the next ones.

3. we want to avoid managing our applications in many different places

It's possible, in next rancher versions to add the repos in the kubectl image ?

Hello @stocky-account-63046 Have you any news of this problem ?