basically just following this code sample:
# Install OLM (Operator Lifecycle Management)
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.16.1/crds.yaml
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.16.1/olm.yaml
kubectl get olm -A
# Install ECK/Elasticsearch Operator
kubectl apply -f https://download.elastic.co/downloads/eck/1.2.1/all-in-one.yaml
# Create a namespace for logging
kubectl create ns logging
# Install Elasticsearch cluster
cat <<EOF | kubectl apply -n logging -f -
apiVersion: elasticsearch.k8s.elastic.co/v1beta1
kind: Elasticsearch
metadata:
name: quickstart
spec:
version: 7.5.0
nodeSets:
- name: default
count: 1
config:
node.master: true
node.data: true
node.ingest: true
node.store.allow_mmap: false
EOF
# Install Kibana
cat <<EOF | kubectl apply -n logging -f -
apiVersion: kibana.k8s.elastic.co/v1beta1
kind: Kibana
metadata:
name: quickstart
spec:
version: 7.5.0
count: 1
elasticsearchRef:
name: quickstart
EOF
# Install Logging/Fluentd & Fluent Bit Operator inside logging namespace
helm repo add banzaicloud-stable https://kubernetes-charts.banzaicloud.com
helm install --namespace logging logging banzaicloud-stable/logging-operator --set createCustomResource=false
# Install demo app
helm install --namespace logging logging-demo banzaicloud-stable/logging-demo --set "elasticsearch.enabled=True"
# Get the password for Kibana (default user is 'elastic')'
kubectl get secret quickstart-es-elastic-user -n logging -o=jsonpath='{.data.elastic}' | base64 --decode; echo
# Access Kibana dashboard
kubectl port-forward -n logging svc/quickstart-kb-http 5601
What did you expect to see?
a live kibana dashboard
What did you see instead? Under which circumstances?
kibana failing to start
Environment
- ECK version:
1.2.1
- Kubernetes information:
AKS v1.18.19
$ kubectl version
v1.21.3
- Logs:
kubectl describe kibana quickstart -n logging
Warning AssociationError 28m (x4 over 28m) kibana-controller Association backend for elasticsearch is not configured
from inside of the cluster, es is working properly
root@doks-debug:~# curl -u "elastic:XXXXXXX" -k "https://quickstart-es-http.logging:9200"
{
...,
"tagline" : "You Know, for Search"
}