NetworkRouter: Custom name for the auto-created Group?

[YuzuZensai]

I recently migrated from the now deprecated NBRoutingPeer to NetworkRouter (the ingress Helm values block that enables NBRoutingPeer is marked deprecated in favor of NetworkRouter/NetworkResource), and noticed that I lost the ability to control the name of the group that gets created for the routing peer.

On the old NBRoutingPeer controller, the group name was derived from the operator's cluster.name value

// internal/controller/nbroutingpeer_controller.go

// handleGroup creates/updates NBGroup for routing peer
func (r *NBRoutingPeerReconciler) handleGroup(ctx context.Context, req ctrl.Request, nbrp *nbv1.NBRoutingPeer, logger logr.Logger) (*nbv1.NBGroup, *ctrl.Result, error) {
	networkName := r.ClusterName
	if r.NamespacedNetworks {
		networkName += "-" + req.Namespace
	}

// ...

			Spec: nbv1.NBGroupSpec{
				Name: networkName,
			},

This let me set cluster.name in Helm values and get a predictable, and readable group name in the dashboard.
On the current NetworkRouter controller, the name is generated instead

// internal/controller/networkrouter_controller.go

// Calculate unique suffix used for Netbird resources.
sum := sha256.Sum256([]byte(netRouter.UID))
uniqueSuffix := networkID + "-" + fmt.Sprintf("%x", sum[:4])[:8]

// Create the group used by the router to discover peers.
groupAC := nbv1alpha1ac.Group(fmt.Sprintf("networkrouter-%s", netRouter.Name), req.Namespace).
	WithOwnerReferences(ownerRef).
	WithSpec(
		nbv1alpha1ac.GroupSpec().
			WithName(fmt.Sprintf("networkrouter-%s", uniqueSuffix)),
	)
err = r.Client.Apply(ctx, groupAC, client.ForceOwnership)

Manually editing Group.spec.name / or group name in dashboard doesn't work either, since it get reapplied every reconcile.

NetworkRouterSpec has no field to override this either. Only dnsZoneRef, image, logLevel, workloadOverride exist. Would it be possible to add support for a custom group name here, similar to what cluster.name did for NBRoutingPeer? I have several NetworkRouters deployed across different sites, and with the current hashed names it's hard to tell which group belongs to which router.

Thank you.

[tkcontiant]

We also need this functionality with the operator after migrating from NBRoutingPeer to NetworkRouter.

We would like the NetBird routing peer group name to be derived from the NetworkRouter resource name. Currently, the dashboard displays networkrouter--. Our preferred format is:

networkrouter-<NetworkRouter-name>-<hash-if-needed>

Keeping a hash for uniqueness is fine. Including the resource name would make it clear which environment and region each group belongs to when configuring access policies and exit routes.

We also need spec.description to be added as support.

apiVersion: netbird.io/v1alpha1
kind: NetworkRouter
metadata:
  name: <network-name>
  namespace: netbird
spec:
  description: "NetBird routing peers for the production VPC in <region>"
  dnsZoneRef:
    name: <zone>
  image: <my-image-proxy>
  logLevel: info
  workloadOverride:
    replicas: 3