Client-go: Error: error parsing jsonpath {.items[?(!(@.spec.taints))]].metadata.name}, unclosed array expect ]

Created on 30 Apr 2018 · 9Comments · Source: kubernetes/client-go

Hi,

Try to get all untainted nodes from k8s cluster with pure kubectl way.

What happen?

$ kubectl get nodes -o jsonpath='{.items[?(!(@.spec.taints))]].metadata.name}'
error: error parsing jsonpath {.items[?(!(@.spec.taints))]].metadata.name}, unclosed array expect ]

Expectation

Similar output just like:

$ kubectl get nodes -o json | jq '.items[] | select(.spec.taints == null) | .metadata.name'
"ip-172-20-109-153.ap-southeast-1.compute.internal"
"ip-172-20-47-98.ap-southeast-1.compute.internal"

Kubernetes version

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-13T22:27:55Z", GoVersion:"go1.9.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Please let me know if I do anything wrong. Thanks.

lifecyclrotten

Source

zanhsieh

All 9 comments

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

fejta-bot on 29 Jul 2018

😕1

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

fejta-bot on 28 Aug 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

fejta-bot on 27 Sep 2018

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.

k8s-ci-robot on 27 Sep 2018

👎2 😕1

@bimalvasan: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

k8s-ci-robot on 14 Sep 2019

/reopen
/remove-lifecycle rotten

zanhsieh on 15 Sep 2019

@zanhsieh: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

k8s-ci-robot on 15 Sep 2019

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

fejta-bot on 14 Dec 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

fejta-bot on 13 Jan 2020

Was this page helpful?

0 / 5 - 0 ratings