Hi, I'm using ECK 2.9. Here are my es and kibana YAML respectively.
---
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
name: ealsticsearch
spec:
version: 7.17.14
volumeClaimDeletePolicy: DeleteOnScaledownAndClusterDeletion
podDisruptionBudget:
spec:
minAvailable: 2
selector:
matchLabels:
elasticsearch.k8s.elastic.co/cluster-name: ealsticsearch
http:
service:
spec:
type: ClusterIP
ports:
- name: https
port: 9200
targetPort: 9200
protocol: TCP
tls:
selfSignedCertificate:
disabled: true
certificate:
# provide your own certificate
secretName: pt-ssl
nodeSets:
- name: default
count: 3
podTemplate:
spec:
securityContext:
runAsUser: 1234
fsGroup: 1234
initContainers:
- name: sysctl
securityContext:
privileged: true
runAsUser: 0
command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144']
containers:
- name: elasticsearch
env:
- name: PRE_STOP_ADDITIONAL_WAIT_SECONDS
value: "5"
- name: READINESS_PROBE_TIMEOUT
value: "10"
- name: ES_JAVA_OPTS
value: "-Xms1g -Xmx1g"
readinessProbe:
exec:
command:
- bash
- -c
- /mnt/elastic-internal/scripts/readiness-probe-script.sh
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 12
successThreshold: 1
timeoutSeconds: 12
resources:
requests:
memory: 2Gi
cpu: 2
limits:
memory: 2Gi
volumeClaimTemplates:
- metadata:
name: elasticsearch-data # Do not change this name unless you set up a volume mount for the data path.
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 5Gi
storageClassName: rook-ceph-block
// kibana.yml
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
name: elasticsearch
spec:
version: 7.17.14
count: 1
elasticsearchRef:
name: elasticsearch
http:
tls:
selfSignedCertificate:
disabled: true
certificate:
# provide your own certificate
secretName: pt-ssl
After ES cluster are ready, I apply kibana.yml and find it's stuck with the following messages.
Name: elasticsearch
Namespace: elasticsearch
Labels: <none>
Annotations: <none>
API Version: kibana.k8s.elastic.co/v1
Kind: Kibana
Metadata:
Creation Timestamp: 2023-10-23T07:23:43Z
Generation: 1
Resource Version: 3267908
UID: 80f11259-2c30-49bb-81ef-75987799ed25
Spec:
Count: 1
Elasticsearch Ref:
Name: elasticsearch
Http:
Tls:
Certificate:
Secret Name: pt-ssl
Self Signed Certificate:
Disabled: true
Version: 7.17.14
Status:
Association Status: Pending
Count: 0
Elasticsearch Association Status: Pending
Observed Generation: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning AssociationError 115s (x3 over 115s) kibana-controller Association backend for elasticsearch is not configured
Normal AssociationStatusChange 115s kb-es-association-controller Association status changed from [] to [Pending]
I searched a while and all posts showed changing YAML of elasticsearch like below
http:
service:
spec:
type: ClusterIP
ports:
- name: https
port: 9200
targetPort: 9200
protocol: TCP
However, mine has these parts already. Turns out it does not work.
There is nothing value in the operator log, either.
Please help, thanks
