Removal of K3s based apps from TrueNAS

Fair, and we’ve also intentionally not really pushed the envelope on adding new Apps while we were not fully settled on Helm/K3s as the right tool for the job. That became apparent almost on day 1 as the bug tickets and feedback started rolling in :slight_smile:

The new implementation will be a single catalog within the TrueNAS UI, which is fully open and has the same Community/Official/Enterprise train of applications. Pull requests welcome. This will be done for quality and supportability reasons primarily.

However on the flip-side the backend will be much more standard. Meaning we’re vastly simplifying what our middleware touches, and docker/compose will behave like it would on a traditional Linux install. This means it is possible to use 3rd party tools and mechanisms to “drive” docker around. Like Portainer, Dockge or other tools which can help manage your catalog of applications. Any person or group could potentially author their own “Catalog Management UI / Tool” and have it added as an App to our open catalog if they so choose. This means they have flexibility to build an interface as simple or complex as they want for whatever target audience they want to cater towards.

That is a fair point, and I’m not sure if we would try to add that type of integration yet. The reason being based on the numbers and how many people actually use/need ingress in a homelab. Judging from the usage stats, that appears to be a pretty small minority of current SCALE users, far less than <10%.

Haha, I get a chuckle when I see folks bring up PBIs. That was my baby and pretty much a one-man show. I own that one :joy: At the end of the day there turns out to just not be that much demand for a FreeBSD-based desktop. Even trying to get buy-in for FreeBSD on a desktop/laptop with FreeBSD developers was tough, considering 60-75% FreeBSD developers at your typical BSD conference were running MacBooks. Even they had no time for that nonsense :joy:

3 Likes