kubesphere-sigs / fluent-operator-walkthrough Goto Github PK

Hi team,

I followed this guide to use Fluent Bit to collect kubelet logs and forward them to the output Elasticsearch. All CRs have been created, but I don't see the related logs and index in Elasticsearch. There might be a bug in the script or sample code.

kubectl exec -it pod/fluentd-http-0 -n fluent -- sh
/ $ nslookup kubernetes 172.x.x.x
Server: 172.x.x.x
Address: 172.x.x.x:53

** server can't find kubernetes: NXDOMAIN

** server can't find kubernetes: NXDOMAIN

/ $ cat /etc/resolv.conf
nameserver 172.x.x.x
search fluent.svc.cluster.local svc.cluster.local cluster.local ca-central-1.compute.internal
options ndots:5

how to set fluentbit log_level？

I failed to run create-minikube-cluster.sh because docker version is not 18.09 or higher.
we should add docker check before install minikube：

• docker is installed and
• docker version is 18.09 or higher

Maybe , we can add code to automate installation or update docker in script.

Hi all!

I went through the walkthough on my M3 MacBook Pro, and ran into a few issues.

First, when attempting to run the ./create-minikube-cluster-for-mac.sh, I got this error.

Warning: kubernetes-cli 1.29.3 is already installed and up-to-date.
To reinstall 1.29.3, run:
  brew reinstall kubernetes-cli
😄  minikube v1.32.0 on Darwin 14.4 (arm64)
❗  minikube skips various validations when --force is supplied; this may lead to unexpected behavior
✨  Using the hyperkit driver based on user configuration

❌  Exiting due to DRV_UNSUPPORTED_OS: The driver 'hyperkit' is not supported on darwin/arm64

error: no context exists with the name: "minikube"

It seems that the hyperkit driver is not available on Apple Silicon. So I tried starting Minikube without that option (just with minikube start), and got farther.

However, when trying to deploy fluentd using this step, the pod failed to start (CrashLoopBackOff). Checking the logs reveals

exec /fluentd/bin/fluentd-watcher: exec format error

So I think that the fluentd-watcher image that it's trying to use is incompatible with my architecture. However, although I'm relatively familiar with Kubernetes, I'm not as familiar with Minikube, nor dealing with Apple Silicon related architecture issues. Anyone have pointers on how I might be able to work around this?

Thank you!