Its not quite that simple unfortunately. When you’re talking about a “custom app” added through the GUI in Dragonfish, that is still technically a catalog app, since it uses the underlying catalog app to convert your configuration into a kubernetes chart. So your custom apps will still need the migration job to automatically transfer to Electric Eel.
There is a lot more detail about the change, why, and how here: https://www.truenas.com/docs/scale/25.04/gettingstarted/scalereleasenotes/#truenas-apps.
In your case, if you’re using only custom apps with unique IPs, you have a few options.
-
Wait until after June 1 to migrate, accept that your app configurations will not migrate, but your host path storage will (I’d recommend looking to migrate any ixvolumes you have to host paths now regardless of the option you pick–which might require a redeploy of the app in DF but will be a more persistent storage method). That will allow you to redeploy the apps in EE, point storage to the existing locations, and get things back up and running with assigned IPs.
-
Migrate whenever, take advantage of the automatic migration, and just use ports assigned on the host IP until after June 1 when you can assign an IP.
-
Migrate closer to the June 1 deadline to still use automatic migration then have a shorter period using ports or simply do not use those apps until after the deadline and you can update IP assignments.
-
Migrate whenever and ignore the automatic migration. Redeploy the apps as Compose files using the Deploy as YAML option in the UI or manage them with dockge or portainer and apply custom networking that way. There are threads on the forum talking about how to do that.