I am following the below Elasticsearch home page documents for creating a Elasticsearch cluster with 3 master node and 3 data node and 1 Kibana node along with ingress using ECK Operator on my Kubernetes cluster.
NOTE: I am working on ON PREMISES CLOUD.
================
Actually at initially I could not able to deploy Eck operator in my Kubernetes cluster after adding the securitycontext and defaultRuntime and giving allowprivillages I can able to deploy the Eck Operator.
then when i try to deploy the Elasticsearch cluster and Kibana
the health of Elasticsearch cluster is on unknown status and phase in applyingchanges for a long time.Due to this status of Elasticsearch my Kibana pod health is at red, So give the solution to deploy a Elasticsearch cluster using ECK operator on my Kubernetes cluster and I am using (ON PREMISES CLOUD)
You may have a resource limitation that's interfering with getting all of those nodes created.
After running kubectl apply you can check the status of your deployment like this:
kubectl get elasticsearch (replace elasticsearch with the name of the pods you're looking for)
If the output of that command stays in the ApplyingChanges phase (never moving to Ready), run kubectl get pods
If the list of pods provided indicates one or more pods in a "pending" status, run kubectl describe pod <name of pod you want to check> (for example, kubectl describe pod quickstart-es-all-roles-2) and look for warnings, probably due to FailedScheduling. The message associated with the warning may indicate issues about insufficient memory for starting.
You may need to add one or more nodes to the EKS cluster, or reduce the resource utilization in the podTemplate section of the manifest.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.