https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# developer
a
This message was deleted.
s
If the apps are classed as legacy they can't be managed by the new UI. You'll need to enable legacy features to do so
What apps are you trying to use?
a
The problem is : In rancher 2.5 I can edit and update the applications in the new UI. I have updated all my apps and change all annotations to not see resources in legacy App (without that, the new interface does not show my applications). In rancher 2.6 It works fine before I upgrade cluster Kubernetes version in some of my cluster. For one cluster I can upgrade this migrated applications in the new Rancher UI but in tow cluster I can't and I have this message. I don't want to use the legacy part and only the new Rancher part. My apps are correctly saw in helm 
helm list -A
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
s
Which version of helm are you using?
a
v3.7 in local to check that and the rancher helm version in rancher
s
I'm not sure of the path your apps have taken, particularly manually changing annotations to work around parts of the UI. From my understanding legacy apps are helm v2 based and that's why the dashboard can't manage them via helm v3. What helm version did they originally start with?
a
helm v2 and tiller (I remove all annotations and replace to show them managed by helm 3). After migration I launch an edit in the new interface of rancher 2.5 and all were upgraded fine
s
ah, ok, you migrated the helm v2 apps to v3?
a
yes. And it works fine if I made a helm upgrade command (this is what I made to avoid this legacy problem)
s
a
No, many apps are tagged with other annotations and with managed by tiller with no reason. I follow this instructions : https://github.com/rancher/rancher/issues/36103#issuecomment-1055153671
s
I'm not 100% sure how your v3 
helm upgrade
works on v2 helm apps, but it's not something we can support
a
the problem is not that, it's just : how to avoid the legacy page warning and upgrade them using rancher and not only helm ?
s
that is the problem though, those legacy warnings are put in place for that specific reason
a
And how I have applications migrated with the same process works fine but not others ?
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.
s
you're trying to work around something that shouldn't be worked around and are getting strange results. the solution is to migrate your v2 apps to v3 by the official helm process
a
The helm steps didn't want to work when I tried. I had to do something else because Rancher in the first 2.x seemed to want to go through tiller and then not by doing helm 3 anyway in the legacy part.
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, ...)
s
The shift of the industry to adopt helm v3 over v2 isn't something in our control, we just follow that. I'm really not sure how your v2 apps are working with v3 upgrade commands, that's something for someone from helm to chime in on. it's a non-standard approach that i don't think even they support
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
a
But It's possible to force rancher to not show specific app as legacy ?
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" ?
s
I'm not aware of a way, that use case isn't something we cover
a
Great, I have a tool I can't use correctly....
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
s
Two of those are the same problem. You'll need to discuss with Helm how to best manage the migrating of apps
a
But I never use helm 2 : only rancher installation part....
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.
s
Can you tell me why you won't use the legacy feature to manage these legacy apps?
a
1. Everywhere we were told to switch to the new interface without openly mentioning the legacy interface 2. I migrated everything to see them in Apps & marketplaces, I can't go back, the resources are no longer linked to the legacy project (except for some configmaps that are seen) and everything was working fine under rancher 2.5. I had to upgrade to 2.6 to update kubernetes above 1.18
3. we want to avoid managing our applications in many different places
s
I'm checking with some colleagues if there's anything we can do for your scenario, however most are US based and won't be online for a while
a
After that, I'm only a week away since I can bypass it via 
helm upgrade
. Thank you 🙂
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 ?
s
I've escalated in another context
a
Hello @stocky-account-63046 What do you mean by "I've escalated in another context" ? Have you any news or something about this problem or how to remove app in legacy part only (and don't remove workloads, services, ...) ?
s
Sorry, i've been away. I haven't found any good news so far but I'm still trying. Generally the same points have been made. Migration of existing apps has never been supported. You might find some help via https://github.com/longhorn/longhorn/issues/3714 (particularly the referenced https://github.com/longhorn/longhorn/issues/3424#issuecomment-998308675).
a
But the helm 2 to helm 3 migration worked well in my case : I can do everything via the helm command. The only problem is that I still have a remnant of the old rancher apps which does not allow me to manage them via app & marketplace in rancher 2.6.
s
I think we're going around in circles here. You used an ad-hoc and unsupported method to migrate helm 2 apps to helm 3. By the sound if it you've done this by tweaking annotations & labels, which even helm doesn't suggest. It's impossible to know what state your apps are in, they may appear via 
list
but it's not known how they report or respond to upgrades, deletions, etc. So even if there was a way to work around the process specifically put in place to split helm 2 and 3 apps there could be additional issues. I genuinely am sorry you've got to this state, I'll continue to seek out someone Rancher side who may be able to help, but otherwise we've reached a dead-end
137 Views
Open in Slack
PreviousNext
Powered by