Good luck!!
Filler, filler
1 Like
My thought was similar a few years ago, but instead of VM, it was all custom apps, so, did that in Kubernetes times (pre Eel). Those custom apps always ran, ran the way I wanted them to not the way the app creator made them and their assumptions, and I do not have any issues ever, updates are flawless (just look at all the nextcloud posts, mine do not do that!). With Eel, instead of just custom app, I have created compose yaml. And, as you say with your VM, no matter what IX does it should work (just like it did before). Unless they remove docker. In your example, they could remove vms, lol!
You are using dockge which is fine, you won’t (for now) see them on the apps screen. I won’t use anything, just the UI. But either way, I expect all will be well from here on out once we all get over the migration. Docker is transportable to just about anywhere so I see little risk moving forward. Hopefully, the last time for major pain.
1 Like
Yes - I have always believed that Docker is a better solution, however the process of switching from K8s to Docker is going to be more painful for some than it needed to be - but once we are all switched over, I think it will be great.
1 Like
Its not our goal to provide any form of “kubernetes 101”, its not our strong suit and we barely have the manpower to provide documentation for our tools (In a lot of cases even that documentation can use some work).
There are docs, tutorials and YouTubers that are more qualified to provide that content than we are at the moment.
Thats also why we’ve clearly communicated that the target audience for clustertool has changed to "Users who know how, and are willing to, maintain their own kubernets cluster.
As we dont think the average SCALE user, is a good fit for maintaining their own kubernets cluster at all.
Simply put: ClusterTool is there to make some frequent tasks easier.
But thats the scope of it.
On nearly every blog we post:
We recommend users review the TrueNAS Software Status page for advice.
Keep posting it yourself, it’s the way we get the word out.
If anyone disagrees with the recommendations, we welcome the feedback.
In a round-about-way I was trying to say:
I have the ability to (and have) ripped the head off my setup. KISS, because if more people start evaluating what is more and/or less important to them instead of trying to assign, define or align with your version of “better”, maybe they will start ripping too–and XYZ then becomes obsolete. So whether you’re a dev or a power user seeking fame and glory; ultimately one person’s solution or setup may not be the best (for me or anyone else) but if you truly want to help people, write documentation/scripts/etc. to offer people a choice or educated guess.
Whenever I hear a developer say that something like documentation or “this or that” is too hard/long/etc. I remember something one of my mentors said to me, that stuck with me: “STFU”.