hermes 6a7ad7e235 fix(hermes): reuse existing ingress resource name (#13)
The merged public Ingress was created as `hermes`, while a legacy `hermes-ui` Ingress with the same host remained in the cluster outside the current Flux inventory. This creates two routes for the same host.

Reuse the existing `hermes-ui` resource name so Flux updates it in place and prunes the inventory-managed `hermes` resource, leaving one route for `hermes.rudolf.keenetic.link`.

Reviewed-on: org1/infra#13
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-18 23:40:13 +01:00
2020-12-02 23:35:47 +03:00
2025-05-16 23:19:05 +02:00
2023-03-11 20:55:38 +01:00
2020-12-02 23:35:47 +03:00
2017-06-08 23:08:24 +03:00
2018-05-02 23:12:40 +03:00
2020-12-02 23:35:47 +03:00
2021-08-19 00:16:56 +03:00
2023-03-11 20:55:38 +01:00
2025-06-02 23:56:25 +02:00
x
2026-11-12 23:08:52 +01:00
2020-12-03 00:22:50 +03:00
2020-12-02 23:35:47 +03:00
2026-11-13 20:24:30 +01:00
2017-11-28 22:58:00 +03:00
2026-10-05 23:54:20 +02:00
2026-11-13 20:24:30 +01:00
2020-12-02 23:35:47 +03:00
2020-12-02 23:35:47 +03:00
2020-12-02 23:35:47 +03:00

Infrastructure repository

See FINDINGS.md for unresolved compliance findings and required follow-up actions.

Manual operations and service documentation

Cluster and production operations

Service documentation

The service-specific Docker documentation remains valid only for services that have not yet been migrated. Update the migration status above and the service documentation when a service moves to Kubernetes.

Repository layout

S
Description
No description provided
Readme
11 MiB
Languages
Python 46.4%
Jinja 32.6%
Shell 14.4%
Dockerfile 6.6%