kubectl wait-for cannot handle JSON path filter expressions like ?(@.x==y)

[andreaskaris]

What happened?

kubectl wait-for cannot handle JSON path filter expressions like ?(@.x==y)

See #1224 (comment)

Even without ||, using ?(x==y) fails to parse, due to this split on =:

Line 208 in [838ae9f](https://github.com/kubernetes/kubectl/commit/838ae9fd9ec21c92d9ad690a902bbbd459f98ee4)
 splitStr := strings.Split(condition, "=")

What did you expect to happen?

Do not split the string on '==' and only on '=' so that JSON path filter expressions are handled correctly

How can we reproduce it (as minimally and precisely as possible)?

The following will fail, yet it should work:

kubectl wait --for='jsonpath={.status.conditions[?(@.type=="Ready")].status}=True' pod/busybox1

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[andreaskaris]

/sig cli

[ardaguclu]

/transfer kubectl

[mpuckett159]

/close
Duplicate of issue here
Please track this issue there. There is a PR to fix this here

[k8s-ci-robot]

@mpuckett159: Closing this issue.

In response to this:

/close
Duplicate of issue here
Please track this issue there. There is a PR to fix this here

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.