ENOTFOUND while installing plugin from command section in deployment file

Elastic Stack Kibana
1

this is my code
lifecycle: postStart: exec: command: - bash - -c - | bin/kibana-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/kibana-plugins/opendistro-alerting/opendistroAlertingKibana-1.13.0.0.zip

this is the error i keep getting and getting my pod in a crashloop

Exec lifecycle hook ([bash -c bin/kibana-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/kibana-plugins/opendistro-alerting/opendistroAlertingKibana-1.13.0.0.zip ]) for Container "kibana" in Pod "kibana-7d97dd46f7-vv5hp_tools(62f1ec74-3350-4dba-8637-77ad6da49e9a)" failed - error: command 'bash -c bin/kibana-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/kibana-plugins/opendistro-alerting/opendistroAlertingKibana-1.13.0.0.zip ' exited with 70: Error: Client request error: getaddrinfo ENOTFOUND d3g5vo6xdbdb9a.cloudfront.net d3g5vo6xdbdb9a.cloudfront.net:443 Plugin installation was unsuccessful due to error "Client request error: getaddrinfo ENOTFOUND d3g5vo6xdbdb9a.cloudfront.net d3g5vo6xdbdb9a.cloudfront.net:443" , message: "Attempting to transfer from https://d3g5vo6xdbdb9a.cloudfront.net/downloads/kibana-plugins/opendistro-alerting/opendistroAlertingKibana-1.13.0.0.zip\nError: Client request error: getaddrinfo ENOTFOUND d3g5vo6xdbdb9a.cloudfront.net d3g5vo6xdbdb9a.cloudfront.net:443\nPlugin installation was unsuccessful due to error \"Client request error: getaddrinfo ENOTFOUND d3g5vo6xdbdb9a.cloudfront.net d3g5vo6xdbdb9a.cloudfront.net:443\"\n"

2

I was able to successfully install this into Kibana 7.11.2. What version of Kibana are you on? Have you verified you can download that file from the container?

3

am running kibana 7.10.2 and yes i was able to install the plugin from inside the container

4

Ok, you were able to install from the container - does that mean this is resolved for you, or is there still an issue?

5

it's still an issue, I want the installation to be automatic whenever the pod is up .

6

I can't honestly say I know where to go from here. If you're able to install the plugin manually, but it's failing in the context of how you're automating the installation leads me to think the issue is somewhere there.

7

Can you provide a minimal reproduction of this issue?

8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.