charts VS otomi-core

Failed to sync TRUENAS catalog: [EFAULT] Failed to clone 'https://github.com/truenas/charts.git' repository at '/mnt/RAID1_18TB/ix-applications/catalogs/github_com_truenas_charts_git_master' destination: Cmd('git') failed due to: exit code(128) cmdline: git clone -v https://github.com/truenas/charts.git /mnt/RAID1_18TB/ix-applications/catalogs/github_com_truenas_charts_git_master stderr: 'Cloning into '/mnt/RAID1_18TB/ix-applications/catalogs/github_com_truenas_charts_git_master'... fatal: unable to access 'https://github.com/truenas/charts.git/': Could not resolve host: github.com '

With these changes now live in 22.12.2, we are now open to collaboration with other App developers on our TrueNAS Apps Catalog hosted on GitHub. Users are encouraged to follow along with incoming changes staged as pull requests, as well as suggestions for new Applications. Aspiring developers can also read through our documentation on App creation and help review pull requests in-flight to ensure the latest and greatest Applications are always available on TrueNAS SCALE for all to run and enjoy.

Error: [EFAULT] Failed to clone 'https://github.com/truenas/charts.git' repository at '/mnt/NAS/ix-applications/catalogs/github_com_truenas_charts_git_master' destination: Cmd('git') failed due to: exit code(128) cmdline: git clone -v https://github.com/truenas/charts.git /mnt/NAS/ix-applications/catalogs/github_com_truenas_charts_git_master stderr: 'Cloning into '/mnt/NAS/ix-applications/catalogs/github_com_truenas_charts_git_master'... fatal: unable to access 'https://github.com/truenas/charts.git/': Could not resolve host: github.com '

Its still there, we are just moving it to a community train. https://github.com/truenas/charts/tree/master/community/chia

Im running the official syncthing app installed from the https://github.com/truenas/charts.git catalogue. Granted it could be the same version of the chart in both catalogues.

An example of a self-hosted Kubernetes-based PaaS is Otomi. Install Otomi on your Kubernetes cluster, compose your platform (by activating the required capabilities) and build, deploy and expose apps in just a couple of minutes. Heroku, but Kubernetes native and running on your own cluster.

This video shows some of the new features of Otomi version 0.19.0 that will be released in Week 11 2023. Follow us on GitHub and be the first to try it out: https://github.com/redkubes/otomi-core

Otomi

Kubernetes is 'only' a multi-node cluster kernel. Some call it the Linux of the cloud.

And because K8s is only a kernel, there are now over 2000+ (open source) projects, all adding some extra functionality to it. Be it for observability, security, or networking. But all of these projects don't really collaborate and end-users don't ask for maturity of individual projects, they want sets/stacks of projects that integrate well.

Now every company has created some Stack with applications and configurations for Kubernetes, all trying to reinvent the wheel and spending an often shocking $ in doing so.

So here is my take:

- Let's create a new category in the Cloud Native Computing Foundation (CNCF) landscape and call it Integrated Stacks for K8s

- To be accepted, a stack needs to provide an open integration framework for other projects to add/integrate their apps

- Just like aLinux distro, each stack is ideal for some specific use case(s)

- A stack can be installed in one run, contains integrated apps that work out-of-the-box, has a (web) UI that acts as a desktop environment to provide easy and secure access to all features. Call it a new user experience for Kubernetes

Wouldn't it be great to have a list of all Kubernetes stacks available that everyone can use (and contribute to)? Just like (in the Linux analogy) you can choose between Linux Mint, Fedora, or Ubuntu.

We already created the first: https://github.com/redkubes/otomi-core