• 4 Posts
  • 88 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • It looks safe to me in the sense that I don’t see any malicious code in here. I don’t think the committee is trying to sneak in security hopes or similar. So all good on from that perspective.

    It’s a very simple helm chart which is consideration! Here’s the thing with charts. They’re meant to be an official means of distributing your app’s manifests for k8s. One package with all runtime needs defined. If the chart supports every tweak I need, then it’s great! If it doesn’t, then I need to modify it myself. This usually means forking the project, making edits, and templating from the fork. It’s a lot of overhead for end users. If the maintainer is willing, it’s so much easier to create an issue or submit a PR with the needed changes.

    Your project has some stars and forks. People are likely using it. Grats! The helm chart doesn’t like meet everyone’s needs and I would expect this to spur some extra issues and PRs. Is that good or bad? That’s up to you!!









  • I thinki founda small issue though I can’t be sure it’s related to the corrupted data and yesterdays maintenance. It looks like a few of my community subscriptions are a little broken? FYI I’m using voyager on IOS.

    As the server catches up, more content from the last two months has been showing up in my home feed. Fantastic! I decided that I don’t want to subscribe to !dailygames@lemmy.zip anymore. So I looked at my subscriptions, selected dailygames, tapped the “3 dots” menu button, and tried to unsubscribe. However, I subscribed again rather unsubscribed. I then looked at my subscribers again and saw daily games listed twice. Then, I unsubscribed using the same method but this only removed one instance of my subscription to dailygames.

    So the content showed up in my home feed. My subscription was seemingly working fine. But I couldn’t unsubscribe as the subscription was not recognized in some contexts. It really feels like some crossed data in the database. Thankfully, this is a very small issue.

    I have at least one more subscription that’s showing the same problem.

    Lastly, I did find a solution. Voyager’s list of community subscriptions allows you to swipe on a specific community to unsubscribe from it. That worked just fine!



  • Oh I could easily be wrong about forgo having integrated ci/cd already. It’s the only tool I mentioned shove that I have never used before. I’m not a good source on this one.

    But I have used both flux and argo quite a lot. I’ll admit that it flux implementation was bad, but it was just a bad experience for everyone using it with me. It was a memory hog and often created. Very few people understood how to use it correctly. When there were errors with e.g. a helm template, you just had to go looking for issues and read through the log. It moved git tags around so you don’t get a history of what flux was doing. I could probably remember more issues if I tried.

    But none of that was a problem with Argo. We just started using it successfully on day 1. Plus its UI is fantastic and a huge advantage. It’s easy to navigate, spot issues, troubleshoot, etc. It also exposes users to resources they unknowingly create because Argo displays owned resources. This part really helped people understand what was going on in k8s. Oh and argo is very extensible. Maybe flux is too but I haven’t tried.


  • They’re both good and quite similar on the surface. But I find that larger, more complicated uses tend to get messy with gitlab because of the heavy use of bash. However, actions are (always?) written in typescript. If your automation needs a lot of logic to handle varying uses, then it’s nice to avoid bash and code with a more language.

    In other words, I’ve seen a few monstrosities that large companies build into gitlab and yikes!