I have been looking into this for some time. I created ELK which worked quite well on my Macbook Pro. It was using the Docker for Desktop installed kubernetes instance. After I add the all-in-one yaml and launch my file, it works and was ingesting data and effectively using the stack. I was happy! I thought to pass this off to a different machine.
I decided that since it works, I wanted to put it on a raspberry pi. That way I have a static always connected system running, while i work on understanding requirements of building out a cluster.
Machine to Follow:
Hardware: Raspberry Pi 4 with 4G RAM, 32G SD Card.
OS: Ubuntu 64
Software: I installed kubeadm, kubectl to get the K8S running. Then i applied the all-in-one yaml prior to running my elastic files.
Elastic-Operator, a part of the all-in-one file, never initializes. When thinking it would just initialize over days, i ran my yaml file definition and noticed that elastic/kibana never get a status. When doing fresh installs and doing other demos, I noticed that elastic and kibana dont start booting until after the elastic-operator is set up.
I have been trying this over weeks. I have thought it may take a few days or something. Then I started to look at logs as well as describing the elastic-operator to see what is actually going on, and I got a similar error when dealing with some postgres containers. It was giving me an Exec error. So it made me think that the base elastic-operator container is not built for arm64.
I have been looking around, and it said that Elastic will have ARM stuff now since they want to get the product to users that consume it in various formats.
I have been able to reproduce it on all of my PI machines, to the point where it isnt even needing my pod yaml. It just needs to start a local cluster on the pi and then run all-in-one. It works on MacbookPro, but takes like 10 minutes or so to initialize, but it is a format that I already knew worked. It seemed the the issue I was isolating it to was related to Pis and possibly ARM64 Requirements.
Am I doing something wrong or incorrect? Should I be using something else when setting up my own ELK K8S cluster?