rancher/k3k

Different labels within different resources

Open

#165 opened on Dec 23, 2024

View on GitHub
 (0 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

It looks like we have different label keys for different resources, i.e. the server pods have the plain cluster=example-cluster-3, while the workloads have the k3k.io/clusterName=example-cluster-3 one.

I think we should have the prefix when possible, to wrap in a glance all the k3k created labels, and have consistent naming.

Contributor guide

Research direction
Inspect the label assignments for server pods and other resources to identify where the inconsistency arises and standardize with the prefix.
Tech stack
gokubernetes
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75