Query Language
There are some use cases, where you want to restrict the targets discovered by Steadybit. One use case can be that you want to design an experiment and make sure, that there are only targets of a specific Kubernetes cluster affected by the experiment. Another use case is that you want to restrict the available targets when configuring an environment.
Boiling down to a set of targets can result in complex statements. For instance, you want to make sure that the targets are matching some sets of key-value pairs but also not in your production cluster. Expressions like these can now easily be written in Steadybits Query Language. The Query Language is a textual representation of the Query UI but with a more advanced feature set. It allows you to build semantic expression blocks, combining them with other expressions or negating them. The Query UI and the Query Language always come together, so it is up to you to choose the style.
The same query can be expressed with the Query UI on the left and the Query Language on the right
When introducing the Query Language, we added a new tab to the already known query UI. Clicking it will switch the edit mode to the Query Language. The already configured query will be translated into the textual form and rendered within the text editor. You can just go ahead writing your own query expressions in there. Like the Query UI, the editor will provide you with auto-completion on available keys and values.
Please note that the Query UI is limited in regard to the queries you write. For instance, one cannot express a query like (a="b" AND d="e") OR f="g" with the Query UI. The interface will tell you when the query can only be edited with the language editor.
Complex queries can only be edited in the Query language editor.
Keys and values can be compared using =, !=, ~, and !~.
// Simple equals check
k8s.cluster-name="prod"
// Not equals check
k8s.cluster-name!="prod"
// Contains check
k8s.cluster-name~"prod"
// Not contains check
k8s.cluster-name!~"prod"
Simple expressions can be chained with AND & OR.
k8s.cluster-name="prod" OR k8s.cluster-name="staging"
k8s.cluster-name="prod" AND container.host="ip-1-2-3-4"
Expression negation
You can exclude a specific key-value expression using NOT.
// Matches all, but not prod
NOT k8s.cluster-name="prod"
Expression blocks can be encapsulated using parenthesis.
(k8s.cluster-name="prod" OR k8s.cluster-name="staging") AND aws.zone="eu-central-1b"
Quoting
Keys containing special characters can also be quoted to work
// Quoting keys is sometimes necessary
"label.aws:ec2launchtemplate/version"="some value"
Last modified 11mo ago