rancher/k3k

Inconsistencies in labels for cluster pods

Open

#531 opened on Oct 27, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (77 forks)auto 404
good first issueteam/collie

Repository metrics

Stars
 (886 stars)
PR merge metrics
 (PR metrics pending)

Description

If I check the configuration for the server pod, I get the following:

kind: Pod
metadata:
  labels:
    cluster: mycluster
    role: server

But for the kubelet pod, it shows:

kind: Pod
metadata:
  labels:
    cluster: mycluster
    mode: shared
    type: agent

I was thinking maybe it would be useful to change type: agent to role: agent for consistency, perhaps? Also, maybe adding the mode label to the server, though I do not know if that's useful?

I would be willing to implement this myself if I could get a couple pointers in the right direction.

Contributor guide

Research direction
Search the codebase for label definitions, specifically 'type: agent' and 'role: server'. Identify where the labels are set for pods and align the naming to use 'role' consistently. Update the server pod labeling to include a 'mode' label if appropriate after confirming its purpose.
Tech stack
go
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85