prometheus/config/testdata/kubernetes_selectors_pod.good.yml

scrape_configs:
  - job_name: prometheus
    kubernetes_sd_configs:
      - role: pod
        selectors:
          - role:  "pod"
            label: "foo=bar"
            field: "metadata.status=Running"
      - role: pod
        selectors:
          - role:  "pod"
            label: "foo in (bar,baz)"
            field: "metadata.status=Running"
discovery/kubernetes: expose label_selector and field_selector Closes #6096 Signed-off-by: Grebennikov Roman <grv@dfdx.me> 2019-10-03 04:55:42 -07:00			`scrape_configs:`
			`- job_name: prometheus`
			`kubernetes_sd_configs:`
			`- role: pod`
			`selectors:`
discovery/kubernetes: expose label_selector and field_selector Close #6807 Co-authored-by @shuttie Signed-off-by: Aleksandra Gacek <algacek@google.com> 2020-02-07 06:13:44 -08:00			`- role: "pod"`
discovery/kubernetes: expose label_selector and field_selector Closes #6096 Signed-off-by: Grebennikov Roman <grv@dfdx.me> 2019-10-03 04:55:42 -07:00			`label: "foo=bar"`
			`field: "metadata.status=Running"`
discovery/kubernetes: Fix valid label selector causing config error Label selector can be "set-based"(https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#set-based-requirement) but such a selector causes Prometheus start failure with the "unexpected error: parsing YAML file ...: invalid selector: 'foo in (bar,baz)'; can't understand 'baz)'"-like error. This is caused by the `fields.ParseSelector(string)` function that simply splits an expression as a CSV-list, so a comma confuses such a parsing method and lead to the error. Use `labels.Parse(string)` to use a valid lexer to parse a selector expression. Closes #8284. Signed-off-by: Alexey Shumkin <Alex.Crezoff@gmail.com> 2020-12-14 05:49:50 -08:00			`- role: pod`
			`selectors:`
			`- role: "pod"`
			`label: "foo in (bar,baz)"`
			`field: "metadata.status=Running"`