rancher/k3k

Spike - define a default storage class per virtual cluster

Open

#797 opened on Apr 16, 2026

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

targeted mode: shared

Targeted outcome:

A platform admin can define a specific default storage class that might differ from the host default storage class for a virtual cluster or via a virtual cluster policy. A virtual cluster policy could define a unique default storage class applicable to any virtual cluster under the policy.

Currently, the host default storage class is used automatically when a virtual cluster user creates a PVC without specifying storageClassName.

Objective: Define how this can be provided, define user flow/experience

Contributor guide

Research direction
Investigate how to allow a platform admin to set a default storage class for a virtual cluster or via policy. Consider intercepting PVC creation at virtual cluster level and applying a default based on configuration.
Tech stack
go
Domain
devopsinfrastructurecloud
Issue type
Research
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
Kubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40