Fix constructing labelSelector and test label strings #4221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #4219 i added support for multiple labels to query.
However, the way i was constructing the
listOptions
, ended up settingjson
representation of theLabelSelector
instead of actual label query.e.g
kubectl get pods -l key1=value1, key2=value2
After reading this documentation/usage issue, kubernetes/apimachinery#47 i realized there is
"k8s.io/apimachinery/pkg/labels
package that has helpers methods to convert a key value pair to correct string format.Tests not test the label query string.