#Fedihelp #keycloak #HelmChart #k8s
I need a working helmchart for keycloak...
Does that exist? Please help aaaahhhhhhhh
#bitnami is outdated.... KeycloakX doesn't seem to work as well :( This sucks
#Fedihelp #pgbouncer #HelmChart #k8s
I need a working helmchart for pgbouncer....
Does that exist? Please help aaaahhhhhhhh

Moar adventures in #selfhosting for #keyboardvagabond! I think that I finally got the longhorn too-many-s3-calls networking issue resolved https://blog.keyboardvagabond.com/michael-dileos-software-and-tech-blog/longhorns-backup-cost-savings-or-not-getting-surprise-bills

I also found that the #bitnami #helmchart for #harborRegistry didn't get updated with the latest migration they did, so I had to find out that they moved their repositories to `bitnamilegacy` and update my helm chart. That took a while to figure out why the image pulls failed!

@selfhosted
@selfhosting
#kubernetes

Longhorn's Backup Cost Savings - or not getting surprise bills

I'm experimenting with where to put these types of blog posts. I have been putting them on my home server, at gotosocial.michaeldileo.o...

Michael DiLeo's Software and Tech Blog

Thêm MCP server vào Kubernetes dễ dàng với Helm Chart! 🚀 Hỗ trợ stdio qua cầu nối nhỏ, cài đặt qua Helm + port-forward. Đồng thời cấu hình Codex remote và ví dụ Flux. Mình cần phản hồi về tính hợp lý của-defaults, capa test stade/ws/stdio, hoặc điểm bất rõ. #MCP #Kubernetes #HelmChart #SelfHosted #VietnameseTech #ServerSetup #MCPServer #K8s #DevOps

https://www.reddit.com/r/selfhosted/comments/1oe4bsp/run_mcp_servers_on_kubernetes_incl_stdio_looking/

Một Helm Chart mã nguồn mở mới đã ra mắt cho Filebrowser Quantum! Đây là giải pháp thay thế đáng chú ý cho Filebrowser đã ngừng hoạt động. Chart hiện ở bản beta v0.8.8, hỗ trợ cài đặt cơ bản và đã được thử nghiệm trên Openshift, Microk8s. Filebrowser Quantum đang nhanh chóng phát triển!

#MãNguồnMở #HelmChart #FilebrowserQuantum #Kubernetes #opensource #SelfHosted

https://www.reddit.com/r/opensource/comments/1nyred7/opensource_helm_chart_for_filebrowser_quantum/

I'm trying to deploy #nextcloud to my #kubernetes cluster using their official #HelmChart . I have a #zfs box, where all my important data lives. I planned to use the csi-nfs-driver to allocate some PVC via NFS. Apparently, there are problems with Nextcloud initializing on NFS backed PVC, because of permissions and rsync and what not. Enabling 'async' for my NFS shares isn't really something I want to do. :-/ There seem to be further problems with RWX volumes on NFS, which is bad for HA as well. Man, this is a headache. Has anybody solved this problem? Adding MinIO to my ZFS host is one option I see. But that adds a lot of complexity 😕
#selfhosting #homelab #k8s
For people running mastodon on Kubernetes with the #mastodon #helmchart, I've submitted the following PR https://github.com/mastodon/chart/pull/166 to update your instance. Feel free to manually apply this patch and upgrade as. there was a security release yesterday #mastoadmin
Update mastodon version by xvilo · Pull Request #166 · mastodon/chart

New security release has been released yesterday, lets update it! My instances has successfully been updated to this new version from the previous version (https://mastodon.org.uk)

GitHub

Знову треба було працювати із #HelmChart. З одного боку це засіб, який спрощує роботу з #kubernetes, але разом з тим наскільки ж багато проблем він додає.

Сам синтаксис шаблону, як тільки він починає містити більше ніж дві умови - починає виглядати дуже страшно. І було б добре, якби не пропустив "-" біля "}}" наприклад, інакше помилку потім можна пів дня шукати.

Tonight

Set up a #kubernetes cluster on #digitalocean
Installed #nginx controller and k8s dashboard
Configured #seleniumgrid with #helmchart especially the hostname with #cloudflare dns and the extra environment variable on #chrome node for managed downloads.
Finally tested with #mocha chai

whoop, got bit when upgrading an old #HelmChart to a new one while using `--reuse-values`

turns out the new helm chart version had updated some of the default values, so... because I used `--reuse-values`, my release kept the old default values from the original version of the chart -- and errored out!

fixed when we removed `--reuse-values` to upgrade the chart 😅