ivanchandRenovate Bot
e6fd58cfc4
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [adguard/adguardhome](https://adguard.com/en/adguard-home/overview.html) ([source](https://github.com/AdguardTeam/AdGuardHome)) | patch | `v0.107.79` → `v0.107.80` | --- ### Release Notes <details> <summary>AdguardTeam/AdGuardHome (adguard/adguardhome)</summary> ### [`v0.107.80`](https://github.com/AdguardTeam/AdGuardHome/blob/HEAD/CHANGELOG.md#v010780---2026-09-03-APPROX) [Compare Source](https://github.com/AdguardTeam/AdGuardHome/compare/v0.107.79...v0.107.80) See also the [v0.107.80 GitHub milestone][ms-v0.107.80]. [ms-v0.107.80]: https://github.com/AdguardTeam/AdGuardHome/milestone/115?closed=1 NOTE: Add new changes BELOW THIS COMMENT. \--> ##### Changed - Client settings in the new web interface: *Use global settings* now applies to Protection only, blocked services have a separate *Use global blocked services* switch, and upstream DNS servers and the DNS cache are always editable. ##### Fixed - Invalid SVCB record from DDR when DoH routes are empty. - Schedule shift on clock change cases ([#​8670]). - Incorrect behaviour on the first launch with the `--check-config` flag. - Reading partially received TCP prefix. - A panic when updating AdGuard Home binary via the command line with `use_private_ptr_resolvers` set to true ([#​8613]). - `log.enabled` set to `false` leaving the legacy logger enabled ([#​8565]). - DHCP server persisting uncommitted leases with zero expiry after `DHCPDISCOVER` messages ([#​8572]). - DHCPv4 settings not being saved when an IPv6-capable interface is selected and DHCPv6 is not configured ([#​8608]). - DHCP not being enabled when only the DHCPv6 section is configured. - DHCP IPv4 range subnet validation not working ([#​8609]). - Client ID validation rejecting valid IPv6 CIDRs with an embedded dotted-decimal IPv4 address ([#​8610]). - Client ID validation accepting IPv4 addresses with leading-zero octets (`192.168.01.1`), malformed MAC addresses, and ClientIDs with leading or trailing hyphens. - IP addresses being sorted lexicographically instead of numerically in the web interface ([#​8636]). - Invalid secondary bootstrap resolver IPv4 address ([#​8637]). - The *Server addresses* dialog overflowing horizontally when a long value is entered. Long unbreakable values in the settings rows overflowing the page. - Encrypted DNS server addresses not appearing in the Setup Guide until the page was reloaded after enabling encryption. - Passwords containing emoji being rejected by the first-run setup wizard in the new web interface. - Cache size and TTL override rows being locked while the DNS cache was disabled in the new web interface ([#​8644]). - Tables staying on an empty page after the last row of that page was deleted in the new web interface ([#​8644]). - The *Log out* button opening the login page in a new tab in the new web interface ([#​8661]). - Per-client blocked services schedules being reset when a client was saved in the new web interface ([#​8638]). - Client sub-pages of the new web interface showing the default values instead of the client's settings when opened directly or reloaded. [#​8670]: https://github.com/AdguardTeam/AdGuardHome/issues/8670 [#​8565]: https://github.com/AdguardTeam/AdGuardHome/issues/8565 [#​8572]: https://github.com/AdguardTeam/AdGuardHome/issues/8572 [#​8608]: https://github.com/AdguardTeam/AdGuardHome/issues/8608 [#​8609]: https://github.com/AdguardTeam/AdGuardHome/issues/8609 [#​8610]: https://github.com/AdguardTeam/AdGuardHome/issues/8610 [#​8613]: https://github.com/AdguardTeam/AdGuardHome/issues/8613 [#​8636]: https://github.com/AdguardTeam/AdGuardHome/issues/8636 [#​8637]: https://github.com/AdguardTeam/AdGuardHome/issues/8637 [#​8638]: https://github.com/AdguardTeam/AdGuardHome/issues/8638 [#​8644]: https://github.com/AdguardTeam/AdGuardHome/issues/8644 [#​8661]: https://github.com/AdguardTeam/AdGuardHome/issues/8661 <!-- NOTE: Add new changes ABOVE THIS COMMENT. --> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODEuNSIsInVwZGF0ZWRJblZlciI6IjQ0LjE4MS41IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> --------- Co-authored-by: Renovate Bot <bot@renovateapp.com> Reviewed-on: https://git.ivanch.me/ivanch/haven/pulls/39
Haven
A forever-work-in-progress self-hosted server setup
Runs on a multi-node k3s cluster deployed across VMs and bare-metal hosts.
Application configuration is stored on an NFS share located on a dedicated SSD. This uses nfs-subdir-external-provisioner as a dynamic storage provisioner with PVC-specific paths. Additional data is stored on a NAS exported via NFS.
The cluster runs k3s with nginx as the ingress controller. MetalLB is used in layer 2 mode for load balancing. cert-manager provides a local CA and issues certificates (required by Vaultwarden).
For setup details, see SETUP.md.
The repository name references my local TLD, .haven ;)
Repository Layout
haven/
├── bootstrap/
│ ├── namespaces.yaml # cluster namespaces
│ ├── secretstores.yaml # cluster secret stores for BitWarden ESO
│ ├── address-pool.yaml # cluster IP pool for MetalLB
│ ├── argocd-install/ # Argo CD install manifests + ingress
│ └── root-app.yaml # root Application watching apps/root
├── secrets/
│ ├── adguard.yaml # adguard credentials from BitWarden
│ ├── <app>.yaml # <app> credentials from BitWarden
│ └── ...
├── apps/
│ ├── root/
│ │ ├── kustomization.yaml # points to applicationset.yaml
│ │ └── applicationset.yaml# auto-discovers apps/*/*.yaml
│ └── <namespace>/ # e.g., dev/, default/, infra/, monitoring/
│ ├── <app-1>.yaml # all-in-one manifest per app
│ ├── <app-2>.yaml # ...
| └──── ...