kuma VS jolt

https://github.com/kumahq/kuma is an CNCF OSS service mesh for Kubernetes and VMs. We're a control plane on top of Envoy proxy. Very actively developed project, some big adopters in the community, and we've just refreshed all of our Good First Issues.

And not just "Kuma" : https://github.com/kumahq/kuma

Another important change to make is that when you create the cluster, change the Nodes in the "Default pool" to use the COS (not COS_CONTAINERD) image type. There are some underlying issues when using Kuma with GKE, as noted in this GitHub issue, and this is the currently recommended workaround. Otherwise, you will hit pod initializing issues that affect certificate provisioning.

Taking things to a broader level, Kuma is another platform agnostic-OSS solution for service mesh and microservice management – with control plane support of Kubernetes, virtual machines (VM), and even bare-metal environments. Kuma was donated to the Cloud Native Computing Foundation (CNCF) by Kong and still actively contributes to the evolving code base.

Kuma Kuma, from Kong, prides itself on being a usable service mesh alternative. Kuma is a platform-agnostic control plane built on Envoy. Kuma provides networking features to secure, observe, route, and enhance connectivity between services. Kuma supports Kubernetes in addition to virtual machines.

If you just want movies and shows, check out Jolt. An app I'm building that's meant to be the social hub of your media server.

If you're interested in media serving, Jolt needs a lot of work with many features. The project management isn't quite setup yet for large teams, but I'd be open to chatting about collaboration. :)

I'm working on Jolt which syncs with your Jellyfin server and shows movies and shows you've watched, and you can go to your own profile to see a grid of the media.

Combined with GolangCI-Lint, a project I'm working on right now called Jolt makes sure errors are handled, pointers are used correctly, variable naming is following all the conventions and a bunch of more stuff. Setting up a toolchain like this in Python would be a huge pain.

A couple days ago I posted about Jolt, a social hub for media servers that allows users to rate, review, recommend media and track what they've watched as well as add media to their watchlist, and got a very positive response from this subreddit.

I've been working on a platform that generates suggestions for movies based on what users have watched and their ratings of those movies. The project is Jolt, if you guys want to check that out. Now I'm trying to brainstorm a sort of scoring/weighting algorithm that could take more things into account, when overlapping scores are generated based on the parameters outlined.

I'm also currently working on a project - and have been posting some updates here and on r/selfhosted, called Jolt which takes a social approach to discovery. In addition to using TMDB to find popular shows and movies, as well as generating suggestions based on what you like, it allows you and your friends to discover media together, and recommend it to one another.

I am working on a small open-source project at the moment, called Jolt, for which I really want to keep my CI/CD as simple as possible. I have experience in GitLab and Drone pipelines, as well as some others, but with the publicly available GH Actions I'm having trouble setting up something that does the following:

Hey, I noticed we're both working on extremely similar projects. Jolt also tracks what you've watched, allows you to maintain a watchlist, and generates recommendations based on your ratings.

Hey everyone, yesterday I posted about Jolt, which is a social hub for media servers that is meant to be used hand-in-hand with Jellyfin. With some help from the community, I have semi-automatic builds of the Docker image running now in GitHub Actions, which means that an early version is available to test for those interested!