-
Notifications
You must be signed in to change notification settings - Fork 28
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
QSL label query should allow for dashed keyname #134
Comments
formuzi
added a commit
to formuzi/katlas
that referenced
this issue
Mar 7, 2019
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"]{*}
formuzi
added a commit
that referenced
this issue
Mar 21, 2019
* 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: