kubectl get pods --namespace=default -l app=elasticsearch-master
Jump to navigation
Jump to search
kubectl get pods --namespace=default -l app=elasticsearch-master NAME READY STATUS RESTARTS AGE elasticsearch-master-0 0/1 Init:ImagePullBackOff 0 3m40s elasticsearch-master-1 0/1 Pending 0 3m40s elasticsearch-master-2 0/1 Pending 0 3m40s
NAME READY STATUS RESTARTS AGE elasticsearch-master-0 0/1 Init:ErrImagePull 0 4m27s elasticsearch-master-1 0/1 Pending 0 4m27s elasticsearch-master-2 0/1 Pending 0 4m27s
NAME READY STATUS RESTARTS AGE elasticsearch-master-0 0/1 Pending 0 3m3s elasticsearch-master-1 0/1 Pending 0 3m3s elasticsearch-master-2 0/1 Pending 0 3m3s
Minikube (1 node cluster) kubectl get pods --namespace=default -l app=elasticsearch-master -w NAME READY STATUS RESTARTS AGE elasticsearch-master-0 0/1 Running 0 6m32s elasticsearch-master-1 0/1 Pending 0 6m32s elasticsearch-master-2 0/1 Pending 0 6m32s
Failed to load logs: container "elasticsearch" in pod "elasticsearch-master-0" is waiting to start: PodInitializing Reason: BadRequest (400) Solution: If you are using macOS verify that your architecture is supported.
Related[edit]
kubectl get events -A helm install elasticsearch
See also[edit]
- Elasticsearch, installation, ELK, Elastic X-Pack,
elasticsearch.yml, logs, ECK, Elasticsearch curl URLs, Elastisearch REST APIs,/_cat/, /_cluster/, /_xpack/, QueryShardException, Elasticsearch index, ELK backup and restore,elasticsearch-cli, Elasticsearch versions, ElasticSearch Snapshot Lifecycle Management (SLM), Low disk watermark, Elasticsearch storage, Elasticsearch users, Elasticsearch roles, search context, shards, Elastic Cloud, Elastic Licensing, ElasticSearch alerts, ESQL
Advertising:
