fix(k3s): use valid generic namespace names (#18)

Flux reconciliation of PR #17 failed because `hermes_generic1` and `hermes_generic2` are invalid Kubernetes namespace names.

This PR renames them to `hermes-generic1` and `hermes-generic2` in both Namespace manifests and Kustomize overlays.

Validation:
- main render remains byte-identical to admin/main
- generic1, generic2, and root renders succeed with Kustomize v5.8.3
- git diff --check passes
- no underscore namespace names remain

Fixes the Flux dry-run error reported by the live cluster.

---------

Co-authored-by: hermes <hermes@rudolf.keenetic.link>
Reviewed-on: #18
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
This commit was merged in pull request #18.
This commit is contained in:
2026-11-21 13:56:04 +01:00
committed by admin
co-authored by hermes
parent 95edba82bf
commit c0e042f0a0
4 changed files with 4 additions and 4 deletions
@@ -1,6 +1,6 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: hermes_generic1
namespace: hermes-generic1
resources:
- ../generic-base
- namespace.yaml
@@ -1,4 +1,4 @@
apiVersion: v1
kind: Namespace
metadata:
name: hermes_generic1
name: hermes-generic1
@@ -1,6 +1,6 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: hermes_generic2
namespace: hermes-generic2
resources:
- ../generic-base
- namespace.yaml
@@ -1,4 +1,4 @@
apiVersion: v1
kind: Namespace
metadata:
name: hermes_generic2
name: hermes-generic2