envoy-gateway-system: NetworkPolicy

actual-budget/networkpolicy.yaml

@@ -55,29 +55,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

apps/templates/plugin-barman-cloud-helm.yaml

@@ -1,32 +0,0 @@
-apiVersion: argoproj.io/v1alpha1
-kind: Application
-metadata:
-  name: plugin-barman-cloud
-  namespace: argocd
-  finalizers:
-  - resources-finalizer.argocd.argoproj.io
-spec:
-  project: default
-  source:
-    chart: plugin-barman-cloud
-    repoURL: https://cloudnative-pg.github.io/charts
-    targetRevision: 0.8.1
-    helm:
-      values: |
-        # CNPG's barman cloud plugin, which backs the PostgreSQL clusters
-        # up to Garage on the NAS (authentik/postgresql-backup.yaml,
-        # immich/postgresql-backup.yaml). It has to run in the operator's
-        # namespace; the chart gets its TLS certificates from cert-manager.
-        resources:
-          requests:
-            cpu: 10m
-            memory: 64Mi
-  destination:
-    server: https://kubernetes.default.svc
-    namespace: cnpg-system
-  syncPolicy:
-    syncOptions:
-    - ServerSideApply=true
-    automated:
-      prune: true
-      selfHeal: true

authentik/networkpolicy.yaml

@@ -108,8 +108,7 @@ spec:
 ---
 # The CNPG operator checks each instance on its status port and connects to
 # PostgreSQL; the instance manager inside each pod watches its Cluster
-# through the API server. The barman cloud sidecar sends the WAL and the
-# base backups to Garage on the NAS (postgresql-backup.yaml).
+# through the API server.
 apiVersion: networking.k8s.io/v1
 kind: NetworkPolicy
 metadata:
@@ -136,34 +135,3 @@ spec:
             cidr: 192.168.1.204/32
       ports:
         - port: 16443
-    - to:
-        - ipBlock:
-            cidr: 192.168.1.99/32
-      ports:
-        - port: 3900
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

authentik/postgresql-backup.yaml

@@ -1,92 +0,0 @@
-# Backups of authentik's database by CNPG itself, through the barman cloud
-# plugin (apps/templates/plugin-barman-cloud-helm.yaml): a base backup every
-# night, and every WAL segment as soon as it is full or 5 minutes old
-# (archive_timeout). Both go to the bucket cnpg-authentik in Garage on the
-# NAS (nas/garage), so the database can be restored to any moment of the
-# last 30 days. Velero copies the data directory while PostgreSQL runs,
-# which is not a consistent copy.
-# The key is Garage's cnpg-authentik, in Vault as kv/cnpg-authentik-s3; it
-# can only reach this bucket.
-apiVersion: external-secrets.io/v1
-kind: ExternalSecret
-metadata:
-  name: authentik-postgres-s3
-spec:
-  secretStoreRef:
-    name: vault-backend
-    kind: ClusterSecretStore
-  refreshInterval: 15m
-  target:
-    name: authentik-postgres-s3
-    creationPolicy: Owner
-    template:
-      engineVersion: v2
-      data:
-        ACCESS_KEY_ID: "{{ .access_key_id }}"
-        ACCESS_SECRET_KEY: "{{ .secret_access_key }}"
-        # Garage rejects requests signed for another region
-        REGION: garage
-  data:
-    - secretKey: access_key_id
-      remoteRef:
-        key: kv/cnpg-authentik-s3
-        property: access_key_id
-    - secretKey: secret_access_key
-      remoteRef:
-        key: kv/cnpg-authentik-s3
-        property: secret_access_key
----
-apiVersion: barmancloud.cnpg.io/v1
-kind: ObjectStore
-metadata:
-  name: authentik-postgres
-  annotations:
-    # The CRD comes with the plugin's own app
-    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
-spec:
-  retentionPolicy: 30d
-  configuration:
-    destinationPath: s3://cnpg-authentik/
-    endpointURL: http://192.168.1.99:3900
-    s3Credentials:
-      accessKeyId:
-        name: authentik-postgres-s3
-        key: ACCESS_KEY_ID
-      secretAccessKey:
-        name: authentik-postgres-s3
-        key: ACCESS_SECRET_KEY
-      region:
-        name: authentik-postgres-s3
-        key: REGION
-    wal:
-      compression: gzip
-    data:
-      compression: gzip
-  instanceSidecarConfiguration:
-    resources:
-      requests:
-        cpu: 10m
-        memory: 64Mi
-    env:
-      # Newer boto3 adds checksums that S3-compatible stores can reject;
-      # the plugin's docs suggest sending them only when required.
-      - name: AWS_REQUEST_CHECKSUM_CALCULATION
-        value: when_required
-      - name: AWS_RESPONSE_CHECKSUM_VALIDATION
-        value: when_required
----
-apiVersion: postgresql.cnpg.io/v1
-kind: ScheduledBackup
-metadata:
-  name: authentik-postgres-daily
-spec:
-  cluster:
-    name: authentik-postgres
-  # 03:00 UTC, after Longhorn's and Velero's backups; immediate: one right
-  # away, so WAL archiving has a base backup to start from.
-  schedule: "0 0 3 * * *"
-  immediate: true
-  backupOwnerReference: self
-  method: plugin
-  pluginConfiguration:
-    name: barman-cloud.cloudnative-pg.io

authentik/postgresql-cluster.yaml

@@ -8,12 +8,6 @@ spec:
   # start an in-place major upgrade. CNPG filled this in at creation.
   imageName: ghcr.io/cloudnative-pg/postgresql:17.4
   primaryUpdateStrategy: unsupervised
-  # WAL archiving and base backups to Garage, see postgresql-backup.yaml
-  plugins:
-    - name: barman-cloud.cloudnative-pg.io
-      isWALArchiver: true
-      parameters:
-        barmanObjectName: authentik-postgres
   resources:
     requests:
       cpu: 50m

bolletjestrui/networkpolicy.yaml

@@ -54,29 +54,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

freshrss/networkpolicy.yaml

@@ -56,29 +56,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

gateway/networkpolicy.yaml

@@ -0,0 +1,120 @@
+# Envoy Gateway: the controller and the proxy it runs (envoyproxy.yaml).
+# Both reach each other (the proxy gets its config from the controller on
+# 18000) and DNS, and take connections from each other and the node: the
+# API server calls the controller's topology webhook (9443) from there and
+# the kubelet probes come from there too (10.1.7.64 is the node's Calico
+# VXLAN address, projectcalico.org/IPv4VXLANTunnelAddr). Nothing scrapes
+# the metrics on 19001.
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: default
+  namespace: envoy-gateway-system
+spec:
+  podSelector: {}
+  policyTypes:
+    - Ingress
+    - Egress
+  ingress:
+    - from:
+        - podSelector: {}
+    - from:
+        - ipBlock:
+            cidr: 192.168.1.204/32
+        - ipBlock:
+            cidr: 10.1.7.64/32
+  egress:
+    - to:
+        - podSelector: {}
+    - to:
+        - namespaceSelector:
+            matchLabels:
+              kubernetes.io/metadata.name: kube-system
+          podSelector:
+            matchLabels:
+              k8s-app: kube-dns
+      ports:
+        - protocol: UDP
+          port: 53
+        - protocol: TCP
+          port: 53
+---
+# The proxy holds the node's ports 80 and 443 (10080 and 10443 inside) and
+# takes connections there from anywhere: the internet through node001 and
+# the router, the LAN, and pods that call a public hostname. It reaches
+# every app it routes to (pods in any namespace; their own policies decide
+# which port), Home Assistant on 192.168.1.202:8123 (outside the cluster,
+# home-assistant/), and the internet on 443 for Longhorn's OIDC login
+# (authentik's token endpoint, at its public address).
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: proxy
+  namespace: envoy-gateway-system
+spec:
+  podSelector:
+    matchLabels:
+      app.kubernetes.io/name: envoy
+      app.kubernetes.io/component: proxy
+  policyTypes:
+    - Ingress
+    - Egress
+  ingress:
+    - ports:
+        - port: 10080
+        - port: 10443
+  egress:
+    - to:
+        - namespaceSelector: {}
+    - to:
+        - ipBlock:
+            cidr: 192.168.1.202/32
+      ports:
+        - port: 8123
+    - to:
+        - ipBlock:
+            cidr: 0.0.0.0/0
+            except:
+              - 10.0.0.0/8
+              - 100.64.0.0/10
+              - 169.254.0.0/16
+              - 172.16.0.0/12
+              - 192.168.0.0/16
+      ports:
+        - port: 443
+---
+# Everything but the proxy (the controller, and the chart's certgen job on
+# upgrades) reaches the API server (the node, port 16443). The controller
+# also fetches the OIDC discovery document of Longhorn's SecurityPolicy
+# from authentik's public address.
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: control-plane
+  namespace: envoy-gateway-system
+spec:
+  podSelector:
+    matchExpressions:
+      - key: app.kubernetes.io/name
+        operator: NotIn
+        values:
+          - envoy
+  policyTypes:
+    - Egress
+  egress:
+    - to:
+        - ipBlock:
+            cidr: 192.168.1.204/32
+      ports:
+        - port: 16443
+    - to:
+        - ipBlock:
+            cidr: 0.0.0.0/0
+            except:
+              - 10.0.0.0/8
+              - 100.64.0.0/10
+              - 169.254.0.0/16
+              - 172.16.0.0/12
+              - 192.168.0.0/16
+      ports:
+        - port: 443

gatus/networkpolicy.yaml

@@ -83,29 +83,3 @@ spec:
             cidr: 192.168.1.204/32
       ports:
         - port: 16443
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

gitea/networkpolicy.yaml

@@ -55,29 +55,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

immich/networkpolicy.yaml

@@ -73,9 +73,7 @@ spec:
 ---
 # The CNPG operator checks each instance on its status port and connects to
 # PostgreSQL; the instance manager inside each pod watches its Cluster
-# through the API server (the node, port 16443). The barman cloud sidecar
-# sends the WAL and the base backups to Garage on the NAS
-# (postgresql-backup.yaml).
+# through the API server (the node, port 16443).
 apiVersion: networking.k8s.io/v1
 kind: NetworkPolicy
 metadata:
@@ -102,34 +100,3 @@ spec:
             cidr: 192.168.1.204/32
       ports:
         - port: 16443
-    - to:
-        - ipBlock:
-            cidr: 192.168.1.99/32
-      ports:
-        - port: 3900
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

immich/postgresql-backup.yaml

@@ -1,97 +0,0 @@
-# Backups of immich's database (albums, faces, the photos' metadata; the
-# photos themselves are files on immich-claim) by CNPG itself, through the
-# barman cloud plugin (apps/templates/plugin-barman-cloud-helm.yaml): a base
-# backup every night, and every WAL segment as soon as it is full or 5
-# minutes old (archive_timeout). Both go to the bucket cnpg-immich in Garage
-# on the NAS (nas/garage), so the database can be restored to any moment of
-# the last 30 days. Velero copies the data directory while PostgreSQL runs,
-# which is not a consistent copy. Only the PostgreSQL 17 cluster; the 14
-# one is about to go.
-# The key is Garage's cnpg-immich, in Vault as kv/cnpg-immich-s3; it can
-# only reach this bucket.
-apiVersion: external-secrets.io/v1
-kind: ExternalSecret
-metadata:
-  name: immich-postgres-17-s3
-  namespace: immich
-spec:
-  secretStoreRef:
-    name: vault-backend
-    kind: ClusterSecretStore
-  refreshInterval: 15m
-  target:
-    name: immich-postgres-17-s3
-    creationPolicy: Owner
-    template:
-      engineVersion: v2
-      data:
-        ACCESS_KEY_ID: "{{ .access_key_id }}"
-        ACCESS_SECRET_KEY: "{{ .secret_access_key }}"
-        # Garage rejects requests signed for another region
-        REGION: garage
-  data:
-    - secretKey: access_key_id
-      remoteRef:
-        key: kv/cnpg-immich-s3
-        property: access_key_id
-    - secretKey: secret_access_key
-      remoteRef:
-        key: kv/cnpg-immich-s3
-        property: secret_access_key
----
-apiVersion: barmancloud.cnpg.io/v1
-kind: ObjectStore
-metadata:
-  name: immich-postgres-17
-  namespace: immich
-  annotations:
-    # The CRD comes with the plugin's own app
-    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
-spec:
-  retentionPolicy: 30d
-  configuration:
-    destinationPath: s3://cnpg-immich/
-    endpointURL: http://192.168.1.99:3900
-    s3Credentials:
-      accessKeyId:
-        name: immich-postgres-17-s3
-        key: ACCESS_KEY_ID
-      secretAccessKey:
-        name: immich-postgres-17-s3
-        key: ACCESS_SECRET_KEY
-      region:
-        name: immich-postgres-17-s3
-        key: REGION
-    wal:
-      compression: gzip
-    data:
-      compression: gzip
-  instanceSidecarConfiguration:
-    resources:
-      requests:
-        cpu: 10m
-        memory: 64Mi
-    env:
-      # Newer boto3 adds checksums that S3-compatible stores can reject;
-      # the plugin's docs suggest sending them only when required.
-      - name: AWS_REQUEST_CHECKSUM_CALCULATION
-        value: when_required
-      - name: AWS_RESPONSE_CHECKSUM_VALIDATION
-        value: when_required
----
-apiVersion: postgresql.cnpg.io/v1
-kind: ScheduledBackup
-metadata:
-  name: immich-postgres-17-daily
-  namespace: immich
-spec:
-  cluster:
-    name: immich-postgres-17
-  # 03:00 UTC, after Longhorn's and Velero's backups; immediate: one right
-  # away, so WAL archiving has a base backup to start from.
-  schedule: "0 0 3 * * *"
-  immediate: true
-  backupOwnerReference: self
-  method: plugin
-  pluginConfiguration:
-    name: barman-cloud.cloudnative-pg.io

immich/postgresql-cluster-17.yaml

@@ -18,13 +18,6 @@ spec:
     shared_preload_libraries:
       - "vchord.so"
 
-  # WAL archiving and base backups to Garage, see postgresql-backup.yaml
-  plugins:
-    - name: barman-cloud.cloudnative-pg.io
-      isWALArchiver: true
-      parameters:
-        barmanObjectName: immich-postgres-17
-
   # Filled once from the PostgreSQL 14 cluster (immich-postgres) after its
   # embedding columns were turned into real[] and pgvecto.rs was dropped,
   # see docs/upgrade-k8s-1.33.md.

mbgwp/networkpolicy.yaml

@@ -85,29 +85,3 @@ spec:
               kubernetes.io/metadata.name: mariadb-system
       ports:
         - port: 3306
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

nas/garage/README.md

@@ -31,12 +31,5 @@ Velero's key is in Vault as `kv/velero-s3` (`access_key_id`,
 `velero/external-secret.yaml`. Without the cluster, `$g key info velero
 --show-secret` on the NAS shows it again.
 
-CNPG's backups (`authentik/postgresql-backup.yaml`,
-`immich/postgresql-backup.yaml`) have a bucket and a key per cluster, so
-neither database can touch the other's backups. Made on 2026-10-26 the
-same way as Velero's, with `cnpg-authentik` and `cnpg-immich` as both
-bucket and key name; the keys are in Vault as `kv/cnpg-authentik-s3` and
-`kv/cnpg-immich-s3`.
-
 Renovate updates the image tag in `compose.yaml`, but nothing deploys it:
 after merging, `docker compose pull && docker compose up -d` on the NAS.

ntfy/networkpolicy.yaml

@@ -65,29 +65,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

renovate.json

@@ -4,7 +4,6 @@
     "config:recommended",
     "customManagers:githubActionsVersions"
   ],
-  "timezone": "Europe/Amsterdam",
   "argocd": {
     "description": "Every app folder; Renovate's regexes are RE2, which has no lookahead, so the other folders are skipped through ignorePaths",
     "managerFilePatterns": [
@@ -89,27 +88,6 @@
         "major"
       ],
       "enabled": false
-    },
-    {
-      "description": "Patch updates of apps that hold little state and are easy to roll back, and of CI's tools, merge themselves once CI passes: three days after the release, in the evening or at the weekend, when the cluster can be reached. Not the databases, operators, Vault, authentik, Longhorn, Velero, immich, Gitea or WordPress. Renovate merges itself; the repo has no branch protection for GitHub's auto-merge to wait on",
-      "matchFileNames": [
-        "ntfy/**",
-        "gatus/**",
-        "freshrss/**",
-        "serpbear/**",
-        "actual-budget/**",
-        ".github/workflows/**"
-      ],
-      "matchUpdateTypes": [
-        "patch"
-      ],
-      "minimumReleaseAge": "3 days",
-      "automerge": true,
-      "platformAutomerge": false,
-      "automergeSchedule": [
-        "* 17-21 * * 1-5",
-        "* 10-21 * * 0,6"
-      ]
     }
   ]
 }

serpbear/networkpolicy.yaml

@@ -54,29 +54,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089

vault/networkpolicy.yaml

@@ -66,29 +66,3 @@ spec:
               - 169.254.0.0/16
               - 172.16.0.0/12
               - 192.168.0.0/16
----
-# cert-manager's HTTP-01 solver, which runs only while a certificate
-# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
-# through Envoy. The policies above let Envoy reach the app's port only,
-# which left the solver unreachable (found 2026-10-26, when ynab's renewal
-# hung).
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: acme-http01-solver
-spec:
-  podSelector:
-    matchLabels:
-      acme.cert-manager.io/http01-solver: "true"
-  policyTypes:
-    - Ingress
-  ingress:
-    - from:
-        - namespaceSelector:
-            matchLabels:
-              kubernetes.io/metadata.name: envoy-gateway-system
-          podSelector:
-            matchLabels:
-              app.kubernetes.io/name: envoy
-      ports:
-        - port: 8089