You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. QSL to support dashed keyname
2. fix full sync API timeout problem after add more k8s clusters
3. support special chars when QSL query is part of http URL, e.g. pod[@containers.$image="k8s.io/test"]{*}
* fix issue #134
1. QSL to support dashed keyname
2. fix full sync API timeout problem after add more k8s clusters
3. support special chars when QSL query is part of http URL, e.g. pod[@containers.$image="k8s.io/test"]{*}
* remove extra tab from log which added by accident
* remove specical chars from returned error message
Currently, it's not possible to structure a QSL query which is looking for keys in the @Label property when those keys have a dash in them.
For example:
node[@labels.$k8s-app="hi"]{} // causes API error
node[@labels.$app="hi"]{} // does not cause API error
This need (to be able to look for key names with dashes) came up in discussion with Adobe in work session to get KAtlas deployed in their infra.
The text was updated successfully, but these errors were encountered: