GoogleCloudPlatform/kubectl-ai

[Feature]: Make resize-pvc eval work well with any type of cluster

Open

#531 opened on Sep 11, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Go (708 forks)auto 404
enhancementgood first issuehelp wanted

Repository metrics

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

Description

Right now, resize-pvc eval has a pretty low success rate on KinD clusters. Per https://github.com/GoogleCloudPlatform/kubectl-ai/pull/319#discussion_r2136601431, we would expect the LLMs to have some trouble getting this right since it's not very compatible with KinD clusters.

Ideally, we would have some way of testing LLMs ability to do this that is a bit more portable and will give us consistent results no matter what type of cluster we use.

Alternatively, we leave things as they are and leave this as a space for LLMs to grow. (apply the correct solution for different cluster types)

Contributor guide

Research direction
Investigate how resize pvc eval currently works and identify KinD specific assumptions. Explore ways to abstract cluster specific logic, possibly using cluster condition checks or mock PVC resize operations.
Tech stack
go
Domain
backenddevops
Issue type
Feature
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.
Half day
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
KubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70