[K3D/K3S] Dynamically egress k3d harmony server IP range #108

Open
opened 2025-08-14 19:25:25 +00:00 by letian · 0 comments
Owner

Current behavior

The k3d harmony server is currently hardcoded in the network policy applied in the context of a local K3d installation. Which is fine in most cases, but sometimes docker might change its subnet and it will silently break the configuration (e.g. Grafana will not be able to query its data source for metrics).

Expected behavior

The subnet should be retrieved dynamically to apply the proper network policy with a local k3d installation. For example, we could use k3d cluster list -o json|yaml and retrieve k3d.cluster.network.iprange, or directly with docker network inspect k3d-harmony.

## Current behavior The k3d harmony server is currently hardcoded in the network policy applied in the context of a local K3d installation. Which is fine in most cases, but sometimes docker might change its subnet and it will silently break the configuration (e.g. Grafana will not be able to query its data source for metrics). ## Expected behavior The subnet should be retrieved dynamically to apply the proper network policy with a local k3d installation. For example, we could use `k3d cluster list -o json|yaml` and retrieve `k3d.cluster.network.iprange`, or directly with `docker network inspect k3d-harmony`.
letian changed title from [K3D/K3S] Dynamically egress k3d harmony server IP to [K3D/K3S] Dynamically egress k3d harmony server IP range 2025-08-14 20:25:15 +00:00
letian added the
Good first issue
label 2025-08-14 20:25:25 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: NationTech/harmony#108
No description provided.