Clarify and enhance JSONPath template syntax

[povsister]

Enhancement Description

• One-line enhancement description (can be used as a release note): Clarify and enhance JSONPath template syntax
• Kubernetes Enhancement Proposal: KEP-1886: Clarify and enhance JSONPath template syntax #1887
• Primary contact (assignee): @povsister
• Responsible SIGs: sig-api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y) TBD
  • Beta release target (x.y) TBD
  • Stable release target (x.y) TBD

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/sig api-machinery
/kind feature

[povsister]

cc @liggitt
You might have some interest on this.

[kikisdeliveryservice]

Hi @povsister

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[povsister]

@kikisdeliveryservice

After discussing with reviewers on the pull-request. I am afraid I can not make it happen in 1.20.
Because the purpose of this enhancement request has been changed from "enhance existing implementation of JSONPath" to "introduce a brand-new implementation of JSONPath"

Kubernetes generally release every 3 month. I see 1.19 released on late Aug, which means code-freeze for 1.20 will probably be early in Nov.
I am a little busy than expected recently, so I can't promise providing a brand-new JSONPath implementation for entire Go community before Nov.

However, I think it's possible to catch up 1.21, I can update the schedule for beta to 1.21 if you wish.

[kikisdeliveryservice]

Thank you for the update @povsister !

Please update the description as you see fit. We will check back in with you in 1.21 and do let us know if anything changes between now and then.

For ref here is the current 1.20 schedule

Best,
Kirsten

[povsister]

No problem.
Thanks for your attention. @kikisdeliveryservice

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[povsister]

/remove-lifecycle stale
I am really busy at the end of year...
Mark it as TODO item in 2021Q1. (For myself)

[deads2k]

I don't think I want to define a new superset of jsonpath for use in kubernetes. I am interested in documenting the current capabilities we have in user level documentation for kubectl and for the API surface we use in places like CRD specs. If someone needs more power, they can pull the json locally and use the library of their choosing.

I don't think user documentation and openapi documentation to clarify what we support require a KEP.

/close

I think it would take a fair amount to convince sig-apimachinery/sig-cli to extend the jsonpath we allow today, but if there are currently unworkable bugs, try pinging in the #sig-api-machinery slack channel and point back to the particular features of the kep you made which are required individually.

[k8s-ci-robot]

@deads2k: Closing this issue.

In response to this:

I don't think I want to define a new superset of jsonpath for use in kubernetes. I am interested in documenting the current capabilities we have in user level documentation for kubectl and for the API surface we use in places like CRD specs. If someone needs more power, they can pull the json locally and use the library of their choosing.

I don't think user documentation and openapi documentation to clarify what we support require a KEP.

/close

I think it would take a fair amount to convince sig-apimachinery/sig-cli to extend the jsonpath we allow today, but if there are currently unworkable bugs, try pinging in the #sig-api-machinery slack channel and point back to the particular features of the kep you made which are required individually.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.