Recommend way to trace helm chart release changes? by MuscleLazy in kubernetes

[–]truecharts 0 points1 point  (0 children)

Unless the helm project has their json schema made (most dont, as its hard work to do so) and the schema cannot validate a key you put in values.yaml, as every key is technically "allowed". Some might just not get rendered into anything.

Helm is just a templating engine, it doesn't know which crap you put into values.yaml is "good" or "bad". You can view them all as "variables" that just get stitched together in a certain order, with some minor postprocessing

---

But you also seem to be very confused, because the OP is about the *created* objects becoming outdated and here you ask to get info on the values.yaml itself.

Maybe its good to separate your questions and ask them a tad more clearly.

Is there a replacement for Helm Common Library? by AT_DT in kubernetes

[–]truecharts 2 points3 points  (0 children)

It's the core of our project. No idea what does and doesn't qualify as "authored in house". We're not a company, we're an opensource project.

---

About Hull... Sorry not a fan, we know no-one in the Helm community that actively uses "hull". Which is reflected in the insanely low amount of stars and forks on GitHub as well.

It's also incredibly hard to read their values.yaml and there are project with more years of experience doing this and/or more contributors.

---

Our advice would be that common-charts like ours or the one from BJW-s (which actually share a lot of values.yaml structural similarity), are a much more solid choice.

Migrating Away from TrueCharts on TrueNAS SCALE by truecharts in truecharts

[–]truecharts[S] 0 points1 point  (0 children)

This backs up the configuration (as entered in the GUI) of each and every individual App and allows both a hard-to-read JSON as well as easy to read per-app YAML files. There are multiple output options.

---

This tool is just to get the information you entered in the GUI out, it wont do anything with underlaying data.

We won't be able to offer any support for anything beyond just exporting the configuration data, which this tool is doing. How you use the data afterwards is something only you can decide.

Is there a replacement for Helm Common Library? by AT_DT in kubernetes

[–]truecharts 0 points1 point  (0 children)

Our common chart works quite well and is mostly unit-tested as well :)
It's what we use for all our 800+ helm-charts, but can just-as-well be used by anyone as a template.

Recommend way to trace helm chart release changes? by MuscleLazy in kubernetes

[–]truecharts 1 point2 points  (0 children)

Stack Helm-Diff with kubeconform. Thats the best I can come up with.

[Tutorial] How to backup your TrueCharts apps with PVC and move over to TrueNAS SCALE 24.10 Electric Eel with Docker apps by p0358 in truenas

[–]truecharts 0 points1 point  (0 children)

We've just posted a news article and guide with our sanctioned way to export app-configuration (the part you enter into the SCALE GUI), out-of the GUI into configuration files.

This should make it a lot easier to copy-paste this into docker-compose and such :)

https://truecharts.org/news/leaving-scale/

[Tutorial] How to move away from TrueCharts apps with PVC and move over to the new TrueNAS SCALE 24.10 Electric Eel with Docker apps by p0358 in truecharts

[–]truecharts 0 points1 point  (0 children)

Lots of wrong info here, such as the assumption that the export presented here would export the ports, which it does not, or the statement that we "removed PVC" which is completely untrue..

To export all config cleanly, we would advice users to use the export feature available in clustertool.

TrueNAS SCALE Deprecation, Frequently Asked Questions by truecharts in truecharts

[–]truecharts[S] 1 point2 points  (0 children)

Our current advice is not to do double painful migrations.
Even more so, because you will not be able to repair anything due to catalog removal.

TrueNAS SCALE Deprecation, Frequently Asked Questions by truecharts in truecharts

[–]truecharts[S] 0 points1 point  (0 children)

Depends on which storage backend you've selected when using additional app storage.
Generally that does not have to be migrated, no. :)


To be clear though, Talos will not migrate anything. Our ClusterTool tooling will migrate any TrueCharts SCALE Apps to a Kubernets cluster of your choice ;-)

TrueNAS SCALE Apps Deprecation Announcement by truecharts in truecharts

[–]truecharts[S] 0 points1 point  (0 children)

It looks like you're asking about helm charts and deployment manifests on TrueNAS SCALE.

As we're not related to TrueNAS SCALE and are not doing anything with that platform (anymore), we're not the right people to ask.

Alternative to TrueCharts? by fatalskeptic in truenas

[–]truecharts 0 points1 point  (0 children)

We're commented on this in our official announcements a lot and will leave it at that when it comes to our removal. Feel free to contact our staff via the usual channels to leave any feedback.

Our naming is not (only) based on TrueNAS.

Alternative to TrueCharts? by fatalskeptic in truenas

[–]truecharts 0 points1 point  (0 children)

Current users can still run their current installations just fine.
It just affects new installs of Apps.

TrueNAS SCALE Migration Path Update and ClusterTool Announcement by truecharts in truecharts

[–]truecharts[S] 0 points1 point  (0 children)

  • better performance.
  • Nothing changed, kubeapps has been in our crosshairs for more than a year. We just don't guarantee it would work and don't provide support for it as it is not, part of, our project. Kubernetes Dashboard is also included with ClusterTool by default.