question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

cannot deploy elasticsearch to kubernetes

See original GitHub issue

Hi,

I’ve been trying to deploy elasticsearch to helm using kubernetes, but I keep getting an exit code 6 or 7 failure after 10seconds. when I get the logs its simply

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:19 --:--:--     0curl: (6) Could not resolve host: elasticsearch-master; Unknown error

this is using the vanilla helm chart from your repo, no changes, on AKS and on prem kubernetes cluster…

output of describe

Name:               elasticsearch-qnuwm-test
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               aks-pool2-46846346-vmss000002/10.240.0.8
Start Time:         Mon, 10 Aug 2020 09:38:43 +0100
Labels:             <none>
Annotations:        helm.sh/hook=test-success
Status:             Failed
IP:                 10.244.3.6
Containers:
  elasticsearch-mqroo-test:
    Container ID:  docker://abcdd32eaff2263b17141b2fd7a1a2ed80801cd869b8472976e64c5a52658b49
    Image:         docker.elastic.co/elasticsearch/elasticsearch:7.8.1
    Image ID:      docker-pullable://docker.elastic.co/elasticsearch/elasticsearch@sha256:54b6af874560621c7791a0845359f2013b42592b18f38857b22fd18246f8afd1
    Port:          <none>
    Host Port:     <none>
    Command:
      sh
      -c
      #!/usr/bin/env bash -e
curl -XGET --fail 'elasticsearch-master:9200/_cluster/health?wait_for_status=green&timeout=1s'

    State:          Terminated
      Reason:       Error
      Exit Code:    6
      Started:      Mon, 10 Aug 2020 09:38:44 +0100
      Finished:     Mon, 10 Aug 2020 09:39:05 +0100
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-vzz6d (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-vzz6d:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-vzz6d
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From                                    Message
  ----    ------     ----  ----                                    -------
  Normal  Scheduled  44m   default-scheduler                       Successfully assigned default/elasticsearch-qnuwm-test to aks-pool2-46846346-vmss000002
  Normal  Pulled     44m   kubelet, aks-pool2-46846346-vmss000002  Container image "docker.elastic.co/elasticsearch/elasticsearch:7.8.1" already present on machine
  Normal  Created    44m   kubelet, aks-pool2-46846346-vmss000002  Created container elasticsearch-mqroo-test
  Normal  Started    44m   kubelet, aks-pool2-46846346-vmss000002  Started container elasticsearch-mqroo-test

Thanks

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:12 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
jmlrtcommented, Dec 10, 2020

still valid 👍 was able to reproduce it and will need to fix helm test pod to handle authentication

0reactions
framsouzacommented, Oct 15, 2021

I assume it was fixed here #1384 , feel free to reopen if it’s not the case.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting methods | Elastic Cloud on Kubernetes [2.5]
If an Elasticsearch node does not start up, it is probably because Kubernetes cannot schedule the associated Pod. First, check the StatefulSets to...
Read more >
How to deploy Elasticsearch on Kubernetes
Make sure that elasticsearchRef is filled with the ES cluster name from the metadata.name field in the elasticsearch. yaml . Under the hood, ......
Read more >
Running & Deploying Elasticsearch on Kubernetes - Sematext
Ensure your cluster has enough resources available, and if not scale your cluster by adding more Kubernetes Nodes. You'll deploy a 3-Pod ...
Read more >
Elasticsearch on Kubernetes - Stateful Application Guide
Each ES master instance has received most of the previous Kubernetes node resources, and K8s cannot deploy Kibana.
Read more >
Troubleshooting Elasticsearch and Setup - IBM
This error indicates that the Kubernetes service account does not have the permissions to deploy to the target namespace any pods that require...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found