knative / knative/serving

KnativeServing - config - features - kubernetes.podspec-persistent-volume-claim/write - but no support for subPathExpr

Open
#16,660 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/feature
Dominant language
Go
Stars
6.1k
Forks
1.2k
Avg merge
2d 7h
Merged PRs (30d)
2

Description

Describe the feature

While activating the features kubernetes.podspec-persistent-volume-claim & kubernetes.podspec-persistent-volume-write allow servicing of pod using persistent volume claim (write mode with isolation subPath attribute), we noticed the usage of the subPathExpr is not allowed.

This silent filtering occurs CRD side + hook validation. I'm told using any dynamic elements to be bad practice in knative developpment, we should allow this fine grained control when required.

I'm currently facing a situation where agnostic, fieldref attributes are required to access specific directory inside a shared pvc.

Would be great to have either ; the subPathExpr policy allowed / not filtered out (while requisting kubernetes.podspec-persistent-volume-claim for instance) OR a new feature, kubernetes.podspec-persistent-volume-claim-subPathExpr like for the sake.

thanks for your feedback,

Kr,

D

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the kubernetes.podspec-persistent-volume-claim feature is represented in the CRD and how hook validation filters subPathExpr. Compare the existing feature policy with the proposed dedicated subPathExpr feature, then confirm the chosen behavior allows the required field without weakening unrelated validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.