Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

app cr downwardAPI should support parsing spec fields #1342

Open
jorgemoralespou opened this issue Oct 9, 2023 · 3 comments
Open

app cr downwardAPI should support parsing spec fields #1342

jorgemoralespou opened this issue Oct 9, 2023 · 3 comments
Labels
carvel-accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request

Comments

@jorgemoralespou
Copy link

What steps did you take:
Create an App CR and wanted to reference a image subPath of one of the fetched artifacts with:

template:
  - ytt:
       valuesFrom:
          - downwardAPI:
              items:
                name: subpath
                fieldPath: spec.fetch[?(@.image)].image.subPath

What happened:
I got:

Preparing template values: spec is not found

What did you expect:
I expected to get the subpath from proper resolution of downwarAPI.

Anything else you would like to add:
I've seen in the detailed App spec this comment:

# fieldPath accepts relaxed jsonpath to select metadata fields from the AppCR (name, namespace, uid, labels, annotations)

Related thread in k8s slack: https://kubernetes.slack.com/archives/CH8KCCKA5/p1696521588882029

Environment:

  • kapp Controller version (execute kubectl get deployment -n kapp-controller kapp-controller -o yaml and the annotation is kbld.k14s.io/images): 0.48.0
  • Kubernetes version (use kubectl version) 1.27

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@jorgemoralespou jorgemoralespou added bug This issue describes a defect or unexpected behavior carvel-triage This issue has not yet been reviewed for validity labels Oct 9, 2023
Copy link

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

@github-actions github-actions bot added the stale This issue has had no activity for a while and will be closed soon label Nov 19, 2023
@jorgemoralespou
Copy link
Author

/remove-stale

@100mik 100mik removed the stale This issue has had no activity for a while and will be closed soon label Nov 20, 2023
Copy link

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

@github-actions github-actions bot added the stale This issue has had no activity for a while and will be closed soon label Dec 31, 2023
@renuy renuy removed the stale This issue has had no activity for a while and will be closed soon label Jan 2, 2024
@praveenrewar praveenrewar added enhancement This issue is a feature request carvel-accepted This issue should be considered for future work and that the triage process has been completed and removed bug This issue describes a defect or unexpected behavior carvel-triage This issue has not yet been reviewed for validity labels Jan 9, 2024
@praveenrewar praveenrewar changed the title app cr downwardAPI fails to parse spec fields app cr downwardAPI should support parsing spec fields Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carvel-accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request
Projects
Status: To Triage
Development

No branches or pull requests

4 participants