Due to the problem pointed out here
I am in the process of finding a way of transforming a Legacy App into a new one.
Did a lot of research & the only little point I got from the Rancher team was a lazy pointer to Instruction: How To Migrate Longhorn Chart Installed In Old Rancher UI To The Chart In New Rancher UI | The Longhorn Knowledge Base
& that was it.
Based on that, I have a script, which basically does the same as with the Longhorn app, but you can choose any app, instead.
Problem is now, the official way does not work. There is this line in the original Longhorn script.
At that point of the script, there is no app of the resource type
apps.project.cattle.io, yet. How can it be found in the first place then?
The whole script is based on this line yielding information, when in reality it does not yield any.
That said, I would appreciate more information in general on this topic. To me, who uses Rancher in a professional production environment, it seems like the whole topic of app migration has been kind of swept under the rug by the Rancher team as quickly & silently as possible. There is barely any discussion on this. Only this non-working Longhorn script base & one issue on Github, where someone from the Rancher team said, that one should use the Longhorn script as a base for converting Legacy Apps.
At least, I have still not found a single out-of-the-box solution to this problem created by Rancher’s design choices. No single Kubernetes object or Rancher button, which I can press once to automatically convert all Legacy Apps. Nothing. It’s treated, like it never happend & Legacy Apps are even to be deprecated in a future Rancher version. Really does not make much sense.
Having Legacy Apps in a new Rancher setup is a serious issue for usability & working with existing production setups deployed through an earlier version of Rancher.