Same issue.
After add selfSignedCertificate into ES.
Search by http is correct.
# curl -u "elastic:$PASSWORD" -k "http://xxxxxx:30300"
{
"name" : "es-monitor-es-master-1",
"cluster_name" : "es-monitor",
"cluster_uuid" : "jxYqF_E0QuSAzQsJII63xQ",
"version" : {
"number" : "7.14.1",
"build_flavor" : "default",
"build_type" : "docker",
"build_hash" : "66b55ebfa59c92c15db3f69a335d500018b3331e",
"build_date" : "2021-08-26T09:01:05.390870785Z",
"build_snapshot" : false,
"lucene_version" : "8.9.0",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
But can not connect from kibana.
es_monitor.yaml
# cat es_monitor.yaml
apiVersion: v1
items:
- apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
annotations:
common.k8s.elastic.co/controller-version: 1.7.1
eck.k8s.elastic.co/es-client-timeout: 60s
name: es-monitor
namespace: monitor
spec:
auth: {}
http:
service:
metadata: {}
spec:
ports:
- name: https
nodePort: 30300
port: 9200
protocol: TCP
targetPort: 9200
type: NodePort
tls:
selfSignedCertificate:
disabled: true
certificate: {}
monitoring:
logs: {}
metrics: {}
nodeSets:
- config:
node.data: true
node.ingest: true
node.master: true
count: 3
name: master
podTemplate:
metadata: {}
spec:
containers:
- env:
- name: ES_JAVA_OPTS
value: -Xms2048m -Xmx2048m
name: elasticsearch
resources:
limits:
cpu: "2"
memory: 4Gi
requests:
cpu: "1"
memory: 4Gi
initContainers:
- command:
- sh
- -c
- sysctl -w vm.max_map_count=262144
name: sysctl
resources: {}
securityContext:
privileged: true
- command:
- sh
- -c
- |
bin/elasticsearch-plugin install --batch repository-hdfs
name: install-plugins
volumeClaimTemplates:
- metadata:
name: elasticsearch-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Gi
storageClassName: local-path
status: {}
transport:
service:
metadata: {}
spec: {}
tls:
certificate: {}
updateStrategy:
changeBudget: {}
version: 7.14.1
kind: List
metadata:
resourceVersion: ""
selfLink: ""
Depoly it.
kubectl apply -f kb_monitor.yam
kubectl describe kibana -n monitor
But can not init pod.
# kubectl describe kibana -n monitor
Name: monitor
Namespace: monitor
Labels: <none>
Annotations: common.k8s.elastic.co/controller-version: 1.7.1
API Version: kibana.k8s.elastic.co/v1
Kind: Kibana
Metadata:
Creation Timestamp: 2021-10-18T11:42:16Z
Generation: 2
Managed Fields:
API Version: kibana.k8s.elastic.co/v1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:common.k8s.elastic.co/controller-version:
Manager: elastic-operator
Operation: Update
Time: 2021-10-18T11:42:16Z
API Version: kibana.k8s.elastic.co/v1
Fields Type: FieldsV1
fieldsV1:
f:status:
.:
f:associationStatus:
f:count:
f:elasticsearchAssociationStatus:
Manager: elastic-operator
Operation: Update
Subresource: status
Time: 2021-10-18T11:42:16Z
API Version: kibana.k8s.elastic.co/v1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:count:
f:elasticsearchRef:
.:
f:name:
f:enterpriseSearchRef:
.:
f:name:
f:http:
.:
f:service:
.:
f:metadata:
f:spec:
.:
f:ports:
.:
k:{"port":5601,"protocol":"TCP"}:
.:
f:name:
f:nodePort:
f:port:
f:protocol:
f:targetPort:
f:type:
f:tls:
.:
f:certificate:
f:monitoring:
.:
f:logs:
f:metrics:
f:podTemplate:
.:
f:metadata:
f:spec:
f:version:
Manager: kubectl-client-side-apply
Operation: Update
Time: 2021-10-18T12:42:04Z
Resource Version: 4059719
UID: da795b91-5373-4d7a-9e5d-f8a8ffa43c45
Spec:
Count: 1
Elasticsearch Ref:
Name: es-monitor
Enterprise Search Ref:
Name:
Http:
Service:
Metadata:
Spec:
Ports:
Name: https
Node Port: 30603
Port: 5601
Protocol: TCP
Target Port: 5601
Type: NodePort
Tls:
Certificate:
Monitoring:
Logs:
Metrics:
Pod Template:
Metadata:
Creation Timestamp: <nil>
Spec:
Containers: <nil>
Version: 7.14.1
Status:
Association Status: Pending
Count: 0
Elasticsearch Association Status: Pending
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning AssociationError 7m16s (x5 over 67m) kibana-controller Association backend for elasticsearch is not configured
Any one can help me, very thanks !