#gutenMorgen
Habe gerade mal geguckt, ob ich vielleicht dem einen oder anderen Kommentar nicht genügend Aufmerksamkeit geschenkt habe. Nope.
Es gab‘ mir aber die Inspiration, ein bisschen Angeln zu gehen…
ICH EMPFEHLE, BEIM FAHRRADFAHREN EINEN #HELM ZU TRAGEN!
*setzt sich mit Kaffee und Schrotflinte in den Lieblingssessel*
🚀 Deploy #Flowise + #Kubernetes + #Helm on #Ubuntu #VPS (10-Step Guide)
Here’s a step-by-step guide to deploy FlowiseAI (commonly just Flowise) on a Ubuntu VPS using Helm + Kubernetes. I assume you have a Ubuntu server (or VPS) and you’re comfortable with shell commands and basic Kubernetes.
I’ll walk you through setting up Kubernetes (if not already), installing Helm, and deploying the Flowise helm ...
Continued 👉 https://blog.radwebhosting.com/deploy-flowise-kubernetes-helm-on-ubuntu-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #opensource #selfhosted #selfhosting
Heck yeah, we have a headscale helm chart now! On codeberg! :heart_cyber:
The #Helm Chart was also updated
https://github.com/openbao/openbao-helm/releases/tag/openbao-0.25.0
Helm chart maintainers should provide a list of container images for each version of a Helm chart to make mirroring for air-gapped deployments easier.
We got headscale up using wrenix's chart!
https://codeberg.org/wrenix/helm-charts/src/branch/main/headscale
Now onto headplane! :heart_cyber:
Wenn dir danach ist, dann zieh dir eine gelbe #Warnweste an.
Wenn du dich mit #Helm besser fühlst, zieh einen an.
Wenn du eine #Sonnenbrille tragen möchtest, dann trag eine.
Aber zwing mich als #RadfahrerIn nicht zu anderen Dingen, als du #Autofahrende zwingen würdest.
Weil wenn du das tust, dann möchtest du nur das Radfahren verhindern.
Is there a way to tell lua file patterns to exclude something? I am struggling so badly with this right now :thinkies:
I want it to always use my special schema from datree.io for files ending in _argocd_appset.yaml or _argocd_app.yaml, but then fall back to the default kubernetes schema if those aren't matched. It should never use BOTH the datree and the default kubernetes schemas, but I have no idea how to say that in lua file pattern matching syntax... It always needs to match stuff under a templates directory btw, because helm.
config = {
schemas = {
["https://raw.githubusercontent.com/datreeio/CRDs-catalog/main/argoproj.io/application_v1alpha1.json"] = "templates/**_argocd_app.yaml",
["https://raw.githubusercontent.com/datreeio/CRDs-catalog/main/argoproj.io/applicationset_v1alpha1.json"] = "templates/**_argocd_appset.yaml",
kubernetes = "templates/**!(argocd_app.yaml)",
},
completion = true,
hover = true,
}
I've tried a number of things, but I'm starting to wonder if this is even possible?
I tried the following, but they don't seem to work:
templates/**!(argocd_app.yaml)templates/**!{argocd_app.yaml}templates/**![argocd_app.yaml]templates/**[!argocd_app.yaml]The config I'm trying to get work is this helm language server:
https://github.com/mrjosh/helm-ls/tree/master?tab=readme-ov-file#default-configuration
It normally works like a charm, but struggles on special CRDs, which would be fine if it let me override just those and not just end up using both default k8s object schemas AND the special CRD schemas...
I really need both the power of helm templating syntax highlighting and autocompletion/validation AND validation of specific templated special CRDs, but this is proving harder than it should be and I know it's probably just like, one character away from working if it's meant to work at all...
Update: click this post to see the thread, it did not go well :[
Verkehrsgerichtstagspräsident empfiehlt, Ansprüche für Radfahrer zu kürzen, wenn sie bei einem Unfall keinen #Helm tragen
[€]
Northeim (ots) - Nörten-Hardenberg, Bahnhofstraße, 29.01.2026, 15.10 Uhr NÖRTEN-HARDENBERG (Wol) Am Donnerstag gegen 15.10 Uhr bemerkte ein Polizeibeamter, welcher sich privat in der Industriestraße in Nörten-Hardenberg befand, dass ein ...
Paderborn-Wewer (ots) - (md) Am Montag, 26. Januar, kam es zwischen 8.00 Uhr und 8.10 Uhr auf dem Steinweg in Paderborn-Wewer zu einem Unfall zwischen einem Pkw und einer Pedelec-Fahrerin, bei der sich die Radlerin leicht verletzte. Der oder die ...
https://www.presseportal.de/blaulicht/pm/55625/6206950
#E-Bike #Helm #Invalidität #Pedelec #Personenkraftwagen #Pkw #Radsport #Transport #Unfall #Verkehrsunglück
5 Fahndung nach den #Linksextremisten von der #Vulkangruppe bei der man nicht weiß ob es sie überhaupt gibt
6 #Licht Bänder
7 Menschen beim einsteigen in den #ICE im #Hauptbahnhof
8 #Arbeiter mit #Helm
@daenumullis.bsky.social
Wer im Dienst keinen #Helm trägt, ist selber schuld.
#Helpflicht für Einsatzkräfte!
Und KI-Verbot für Foto-Veröffentlichungen staatlicher Stellen.
🏡 + 🚀 = DevOps bliss! I'm running my GitLab runners via helm charts on a home K8s cluster now, ditching free runners & avoiding VPS rental headaches! Control, flexibility, and cost savings! 💰 Check out my guide: https://bit.ly/45CgJRD #Kubernetes #GitLab #DevOps #HomeLab #CICD #Helm #docker
🚀 Deploy #Flowise + #Kubernetes + #Helm on #Ubuntu #VPS (10-Step Guide)
Here’s a step-by-step guide to deploy FlowiseAI (commonly just Flowise) on a Ubuntu VPS using Helm + Kubernetes. I assume you have a Ubuntu server (or VPS) and you’re comfortable with shell commands and basic Kubernetes.
I’ll walk you through setting up Kubernetes (if not already), installing Helm, and deploying the Flowise helm ...
Continued 👉 https://blog.radwebhosting.com/deploy-flowise-kubernetes-helm-on-ubuntu-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #opensource #selfhosted #selfhosting
Never thought I'd say this but #GitLab seems to be the better option for hosting a #Helm chart repository and a #Container registry than #GitHub... esp a private one. You could even do this from a single #Git repo (project) on GitLab, which also means you could even just create a single access token that is scoped to just this repo to have access to the hosted Helm charts and container images. Pretty nuts?
GitHub, otoh, I don't think you could even have a token that is as fine-grained scoped like this - to give access to a Helm chart (using the #OCI package registry route) or a container image means to give access to ALL of them belonging to the user/org. Am I wrong? Anyway, I wonder how does other options like #Forgejo compare to these two. Big W for GitLab though.
How do you manage your #Kubernetes resource lifecycle?
Let's say you installed a new product, with all the bells and whistles (deployments, service accounts, gateway, network policies, roles and bindings. But you don't need those anymore. How do you dispose of them?
Do you install stuff with a kubectl apply and do you dispose of them by manually calling kubectl delete?
Do you rely on #Helm/#Nelm to install/uninstall and create your own Charts?
Do you use #Terraform/#Opentofu with the hashicorp/kubernetes provider to map the K8S resource lifecycle to a TF resource lifecycle?
Do you use something else? If so, can you elaborate?
Vaikka periaatteessa eutanasiaa kannatankin, Sarah Helmin Ravensbrück-kirjan kuvaukset natsien vuonna 1940 saksalaisissa parantoloissa aloittamasta "arvottomien elämien" tuhoamisesta arveluttavat nykyisessä maailmantilanteessa. "..ilmaisuja kuten 'tyhjät ihmisakanat' ja 'painolastielämät' oli käytetty yleisesti eugeniikan näennäistieteessä Saksassa ja monissa muissa maissa, erityisesti Yhdysvalloissa 1800-luvulta lähtien."
#Helm #Ravensbrück #eugeniikka #eutanasia #ihmisroskat
