Running the Elastic Stack on Kubernetes with ECK
Вставка
- Опубліковано 4 жов 2020
- Elastic Cloud on Kubernetes (ECK) automates the deployment and orchestration of the Elastic stack on Kubernetes. Come learn how things work under the hood to understand how ECK manages Elasticsearch clusters. We'll talk about Kubernetes concepts, operators, reconciliation loops and nodes orchestration.
Thank you to our presenter, Sebastien Guilloux.
Be sure to join your local Elastic Virtual User Group to stay up-to-date on upcoming meetups: community.elastic.co/
Questions? Check out discuss.elastic.co/
Connect with the Elastic community through Slack: ela.st/slack
... I see the crd's and assuming the operator pod are all created inside the elastic-system namespace...
but looking at the quickstart, no where is it implying into which namespace to push it to... would it make sense to do it into a different namespace and leave elastic-system for the operator, back end supporting bits or is engineering happy that we create our clusters inside it also, thinking a separate ns is best, then you can create multiple clusters, if you want to for whatever strange idea... each isolated from each other and from the operator bits ?
how to access or send request to elasticsearch cluster from other container (POD which is running different application for ex. nodejs).
I tried deploying ECK quickstart to my k8s cluster but it can't create persistent volume
any video for user authentication ?
I was hoping this one would use that. A major change and no real tutorials
If I delete master node with ECK deployed elasticsearch, it cant connect to existing cluster but if an update happens to an Elasticsearch CRD it can patch the master node by restarting it. how does it work? what if due to some reason master node goes down would it be able to pickup from there ? because deleting it manually runs into all sorts of issue.
Hi Ojas! That's a great question for discuss.elastic.co or our public slack workspace (ela.st/slack). Both of those spaces are monitored by technical folks, unlike this comment section :)
Why elastic eck needs privilege SCC in openshift ?
ECK itself doesn't need privileged SCC. You also don't need a privileged SCC to deploy Elasticsearch, Kibana, APM Server, or Enterprise Search. The only place where you do need a privileged SCC is to deploy Beats or Agent in order to collect logs and metrics on your Kubernetes cluster. See www.elastic.co/guide/en/cloud-on-k8s/master/k8s-openshift-beats.html.