{"id":738,"date":"2021-04-26T11:15:30","date_gmt":"2021-04-26T09:15:30","guid":{"rendered":"https:\/\/www.ume.li\/blog\/?p=738"},"modified":"2021-04-26T12:56:17","modified_gmt":"2021-04-26T10:56:17","slug":"access-your-index-elastic-search-queries","status":"publish","type":"post","link":"https:\/\/www.ume.li\/blog\/2021\/04\/26\/access-your-index-elastic-search-queries\/","title":{"rendered":"Access your index – Elastic Search queries"},"content":{"rendered":"

HCL Component Pack is fully set-up now, you’re interested what’s going on in that mysterious elasticsearch part? In CP 6.5 you’ve been able to access the ElasticSearch data directly through the kibana pod. With CP7 this seems to be gone.<\/p>\n

If you really want\/need to access the ElasticSearch environment, you may use the following path on your own risk<\/p>\n

Step 1: get the necessary certificates<\/p>\n

\r\n#!\/bin\/sh\r\n\r\necho "check directory"\r\ncwd=`pwd`\r\nif [ ! -d "$cwd\/certs" ]; then\r\n mkdir -p $cwd\/certs\r\nfi\r\nversion='elasticsearch-7-secret'\r\n#version='elasticsearch-secret'\r\necho "extract certificates"\r\nif [ ! -f "$cwd\/certs\/elasticsearch-healthcheck.crt.pem" ]; then\r\n\tkubectl view-secret -n connections $version elasticsearch-healthcheck.crt.pem > $cwd\/certs\/elasticsearch-healthcheck.crt.pem\r\nfi \r\nif [ ! -f "$cwd\/certs\/elasticsearch-http.crt.pem" ]; then\r\n\tkubectl view-secret -n connections $version elasticsearch-http.crt.pem > $cwd\/certs\/elasticsearch-http.crt.pem\r\nfi\r\nif [ ! -f "$cwd\/certs\/elasticsearch-healthcheck.des3.key" ]; then\r\n\tkubectl view-secret -n connections $version elasticsearch-healthcheck.des3.key > $cwd\/certs\/elasticsearch-healthcheck.des3.key\r\nfi\r\n\r\necho "done"\r\n<\/pre>\n
This script requires the kubectl krew plugins<\/a> installed in your kubectl client.
\nRun this on your master or a client which has kubectl and the krew plugin installed to get the secrets. <\/p>\n
Then you could use the following script as an example:<\/p>\n
\r\n#!\/bin\/bash\r\n# An util script so that you can interact with es like what official site suggested:\r\n# for additional usage, if you need to do much more complicated operation, pls\r\n# refer to offcial site:\r\n# https:\/\/www.elastic.co\/\r\n\r\n\r\nset -o errexit\r\nset -o pipefail\r\nset -o nounset\r\n\r\n# the directory that all cert placed\r\n# change this to your cert directory.\r\ncert_dir=.\/certs\r\nHOST=`hostname`\r\nURL_base="https:\/\/localhost:30098"\r\n#CP6.5:\r\n#URL_base="https:\/\/localhost:30099"\r\n#CP6.5: KEY_PASS=`kubectl view-secret -n connections elasticsearch-secret elasticsearch-key-password.txt`\r\n\r\nKEY_PASS=`kubectl view-secret -n connections elasticsearch-7-secret elasticsearch-key-password.txt`\r\n\r\necho "[$KEY_PASS]"\r\nif [ "${1:-}" = "" ] || [ "${2:-}" = "" ]; then\r\n  echo "usage: sendRequest.sh   param_method param_url [additional param]"\r\n  echo "Request is send to es client(coordinating node) by default. add param"\r\n  echo "to send request to es master node"\r\n  echo "refer: https:\/\/www.elastic.co\/guide\/en\/elasticsearch\/reference\/current\/modules-node.html"\r\n  exit 107\r\nfi\r\n\r\n# save the HTTPS METHOD.\r\n_method=$1\r\n# and then shfit this argument.\r\n# since we need to pass the rest args to curl command unchanged.\r\nshift 1\r\n\r\n# turn off expansion to avoid asterisk becoming current directory\r\nset -f\r\n# please ensure those\r\n#   cert, password, key, cacert\r\n# are at the right location.\r\nresponse_text=$(curl \\\r\n   --insecure \\\r\n   --cert $cert_dir\/elasticsearch-healthcheck.crt.pem:${KEY_PASS} \\\r\n   --key  $cert_dir\/elasticsearch-healthcheck.des3.key \\\r\n   --cacert $cert_dir\/elasticsearch-http.crt.pem \\\r\n   -X${_method} \\\r\n   ${URL_base}"$@")\r\n\r\n# echo to return to caller.\r\necho ${response_text}\r\n# turn expansion back to 'on'\r\nset +f\r\n<\/pre>\n
Now you can use it like this<\/p>\n
\r\n.\/sendRequest.sh GET \/_cat\/indices > indices.txt\r\n<\/pre>\n
Disclaimer: use at your own risk<\/p>\n","protected":false},"excerpt":{"rendered":"
HCL Component Pack is fully set-up now, you’re interested what’s going on in that mysterious elasticsearch part? In CP 6.5<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[62,54,23],"tags":[],"class_list":["post-738","post","type-post","status-publish","format-standard","hentry","category-62","category-component-pack","category-connections"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t