Scrape more information from _cluster/health es end point

[ewolinetz]

Addresses https://jira.coreos.com/browse/LOG-377

compared to:

$ oc exec -c elasticsearch example-elasticsearch-cdm-pjdp5067-1-bc779dd6d-2g8p9 -- es_util --query=_cluster/health?pretty
{
  "cluster_name" : "example-elasticsearch",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 2,
  "number_of_data_nodes" : 2,
  "active_primary_shards" : 1,
  "active_shards" : 1,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0
}

status:
  clusterHealth:
    activePrimaryShards: 1
    activeShards: 1
    initializingShards: 0
    numDataNodes: 2
    numNodes: 2
    pendingTasks: 0
    relocatingShards: 0
    status: green
    unassignedShards: 0
  conditions: []
  nodes:
  - deploymentName: example-elasticsearch-cdm-pjdp5067-1
    upgradeStatus: {}
  - deploymentName: example-elasticsearch-cdm-pjdp5067-2
    upgradeStatus: {}
  pods:
    client:
      failed: []
      notReady: []
      ready:
      - example-elasticsearch-cdm-pjdp5067-1-bc779dd6d-2g8p9
      - example-elasticsearch-cdm-pjdp5067-2-67b494ff69-z9q9k
    data:
      failed: []
      notReady: []
      ready:
      - example-elasticsearch-cdm-pjdp5067-1-bc779dd6d-2g8p9
      - example-elasticsearch-cdm-pjdp5067-2-67b494ff69-z9q9k
    master:
      failed: []
      notReady: []
      ready:
      - example-elasticsearch-cdm-pjdp5067-1-bc779dd6d-2g8p9
      - example-elasticsearch-cdm-pjdp5067-2-67b494ff69-z9q9k
  shardAllocationEnabled: all

[ewolinetz]

requires #122 to be merged in first

[richm]

/test e2e-aws

[ewolinetz]

@jcantrill should i also update the manifest to expose these status fields for the console?

[jcantrill]

Any reason not to reuse an existing library over writing our own?
Ref:

• https://github.com/PaesslerAG/jsonpath
• https://github.com/buger/jsonparser
• https://github.com/oliveagle/jsonpath

[ewolinetz]

not really... less to vendor in for a single file?

[jcantrill]

If we are comfortable it won't come back to bite us and we can support given our needs, its probably fine.

[ewolinetz]

we can make it a tech debt item to investigate further

[richm]

lgtm - @jcantrill

[portante]

Looks good; not sure I understand all the reason for the function renames.

[portante]

Seems like you have a mix of partial Elasticsearch cluster health data with other kube level stats. Perhaps any way to group these in the file so that in the future folks know that the ES cluster health stats are together?

And are you going to add the rest of them?

[ewolinetz]

This is simply information that gets exposed at the console level. this will configure it to know where to scrape it from on the CR and what to label it as.

[ewolinetz]

this isn't necessary for 4.1.0 -- required for 4.2 as part of the sdk bump

[josefkarasek]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ewolinetz, josefkarasek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ewolinetz,josefkarasek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment