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

Parse Nested Arrays does not work #2368

Open
rajatvig opened this issue Apr 10, 2024 · 1 comment
Open

Parse Nested Arrays does not work #2368

rajatvig opened this issue Apr 10, 2024 · 1 comment
Assignees
Labels
kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@rajatvig
Copy link

Have a custom CRD returning conditions under a nested structure like

status:
  parents:
  - conditions:
    - lastTransitionTime: "2024-04-05T16:27:15Z"
      message: References resolved
      observedGeneration: 1
      reason: ResolvedRefs
      status: "True"
      type: ResolvedRefs
    - lastTransitionTime: "2024-04-05T16:27:15Z"
      message: Accepted HTTPRoute
      observedGeneration: 1
      reason: Accepted
      status: "True"
      type: Accepted
    controllerName: projectcontour.io/gateway-controller
    parentRef:
      group: gateway.networking.k8s.io
      kind: Gateway
      name: contour
      namespace: projectcontour
      sectionName: https

Using StateSet to parse with path ['status', 'parents', 'conditions'] but getting an error like

registry_factory.go:685] "gatewayapi_grpcroute_status" err="[status,parents,conditions]: expected value for path to be string, got <nil>" 

Is this supported?

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 10, 2024
@logicalhan
Copy link
Member

/kind support
/assign @rexagod
/triage accepted

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants