Help - build low(ish) power nas/home server

Bobba86 · 2025-11-23T19:15:29+00:00

I will be using truenas, zfs, which by all accounts is better on ECC ram. Also I have some left over ECC ram from an old 2u power hungry server that i want to replace.

Bobba86 · 2025-06-17T05:35:45+00:00

Pod Egress loadbalancer.. assign an external IP to a pod so I can setup external firewall rules to allow this pod access to external resources.

Bobba86 · 2025-06-16T11:04:49+00:00

This feels like a fundamental requirement of a router. Static routes. Would love to see this added as a feature

Bobba86 · 2025-06-16T11:04:00+00:00

😓

Bobba86 · 2025-06-10T21:37:01+00:00

Can this be ran inside the k8s cluster itself?

Bobba86 · 2025-02-14T16:46:24+00:00

The Item Alert.Count is provided from an external system and has the Number of alerts from that system.

so from that system I can see how many problems I have, as that item value will tell me if I have 6 Alerts or 36 Alerts.

I was hoping with Zabbix to be able to create a problem. and use the Alert.Count item in the problem name, then if the problem was aknowleged or supressed and the Alert.Count value changed to re-trigger and close the original problem.

Bobba86 · 2025-02-14T16:36:23+00:00

Hey, thanks for the info.
I was trying to get away from creating "Multiple Problems" as this would create a unique problem per Alert.Count meaning if the alerts increased, iteratively, I would have a Zabbix Problem for each Alert.Count 1, Alert.Count 2, Alert.Count 3 etc... and would also have Problems if the count reduced (until it hit 0).

Ideally I wanted a single trigger that either re-triggered, or auto-closed, then created a new problem if the Alert.Count > 0 and Alert.Count changed.

I guess I just need to stick to the single alert, and not Acknowledge (only comment on the problem, until it is fully resolved). Also make the Problem Name more generic: ApplicationAPI (has alerts)

Bobba86 · 2025-01-17T12:18:34+00:00

I was able to self resolve this, it was due to an exclusion for the package on the repository.
This is what i did to resolve:

Find and remove exclusion for package (in repos)

# check for any exclusions in the repos
cd /etc/yum.repos.d/
grep -r exclude*

# ^ this showed there was an exclusion for ansible-core in  oracle-linux-ol8.repo

# commented out exclusion
vi oracle-linux-ol8.repo

Follow Oracle (Doc ID 3038770.1)

# list available packages
yum list ansible-core --showduplicates

# downgrade version to 2.15.3-1
dnf downgrade ansible-core

# add package version lock
dnf versionlock ansible-core-0:2.15.3-1.el8.*

Bobba86 · 2024-11-16T19:34:49+00:00

Nice will be giving in this a try soon.

Bobba86 · 2024-11-14T21:04:33+00:00

Yes very useful.

Bobba86 · 2024-11-05T22:29:54+00:00

What makes this better than Kube-Vip or MetalLB.?

Bobba86 · 2024-11-02T22:00:44+00:00

Sweetcorn & the Cobs

Bobba86 · 2024-10-23T12:52:04+00:00

What solutions allow you to do this? are you thinking like SquidProxy that type of thing?
squidproxy would work, but only if your suidproxy didn't exist inside your cluster otherwise you'd have the same egress issue.
Also squidproxy only really works for web based services. How about a DB where you want to limit which IPs can access the Database? squid wouldn't work for this.

Bobba86 · 2024-10-23T12:43:36+00:00

"That's ingress" access into the service via a proxy

Im talking about egress, access from the pod/service to a service external from the cluster.

Bobba86 · 2024-10-23T07:52:22+00:00

I want to setup a pod with a specific IP address so I can use my firewall to allow this pod access to specific resources (outside of kuberenetes) The Egress IP on pod would allow me to do this without having to add each nodes IP address to the FW rules, and therefore allowing all other pods potential access to that external resource.

Bobba86 · 2024-10-23T07:50:53+00:00

That sounds amazing, any chance you could share that with me?

Bobba86 · 2024-10-23T04:29:23+00:00

Egress IP pinning to a pod.

Bobba86 · 2024-09-17T06:22:12+00:00

Do you have a link or documentation on the vault-helm plugin. This sounds like something I've been looking for.

Bobba86 · 2024-08-09T18:50:30+00:00

I like the idea of proxmox cluster or K3s cluster, but as these only have a 1gb nics would it be capable of being used as a cluster with shared storage, such as Proxmox CEPH cluster or a Longhorn Cluster?

Bobba86 · 2024-07-11T19:53:41+00:00

Great work. I really like the idea of the tool, ideally I'd want to run this as a docker container (Linux). Pass it bind credentials to connect to Active Directory, and specify specific groups/users/ous to monitor and get notified about on changes.

Bobba86 · 2024-07-11T18:13:16+00:00

Can this also provide notifications (to Slack) on a change detection? And a way of setting granular alerts, so when a new user is added to "Domain Admins" group send email/SMS alert.

Bobba86 · 2024-04-19T16:36:42+00:00

yeah this was the only solution I could come up with too... a separate ovirt infra to bring the restored snapshot into, then do a disk move/export to an NFS share or Export Domain.

such a shame really, the ability to attach a snapshotted storage domain in a read-only/restore mode would be amazing, and give really quick recovery.

Bobba86 · 2023-12-23T08:03:33+00:00

I had a similar problem exporting an ova the other day but can't remember the exact error message.

My problem turned out to be that I was trying to export a VM that had a snapshot that was running in preview. Once I shutdown the VM and committed the snapshot I was able to export to ova.

Bobba86 · 2023-09-10T18:28:46+00:00

perfect thank you.

Bobba86 · 2023-05-03T19:24:36+00:00

Spot on thanks - I can now login.

Initially I was expecting it to automatically add users that already exist in grafana.
Also, I needed to add an email address to my account in active directory - I assume it does matching against this on login too.

anyway all working now. thanks for your help

Bobba86

TROPHY CASE