GoogleCloudPlatform/kubectl-ai

evals: we should ensure resources in eval tasks must not contain hints to help with the eval tasks

Open

#298 opened on Jun 2, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (708 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (7,532 stars)
PR merge metrics
 (PR metrics pending)

Description

We want to ensure the eval tasks represent realistic scenario and we have observed that name/namespaces of the k8s resources used in the task contains hint to make AI Models aware that these are part of evals or some sort of test. I think this affects the model's performance on the task, so we need to fix it for all the existing tasks.

Contributor guide

Research direction
Scan the repository for all eval task files, locate Kubernetes resource names and namespaces, and rename any that contain hint like words (e.g., 'eval', 'test', 'kubectl ai') to neutral names. Ensure no references to evaluation or testing remain in the resource definitions.
Tech stack
go
Domain
devops
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
GitKubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70