-
Notifications
You must be signed in to change notification settings - Fork 774
Open
Labels
>enhancementEnhancement of existing functionalityEnhancement of existing functionalitydiscussWe need to figure this outWe need to figure this out
Description
We currently set the config.server.name for Kibana instances to the name of the Kibana CRD. Code link. Some Kibana documentation indicates that the server.name needs to be distinct for each instance behind a load balancer. This hasn't changed for ~6 years, but also causes issues in stack monitoring where the Kibana instances (if > 1) show up as the Kibana CRD name and not the Pod name.
Potential solutions:
- Just not set it. The documentation suggests that it defaults to the hostname.
- Set this via the downward api:
podTemplate:
spec:
containers:
- name: kibana
env:
- name: SERVER_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
Metadata
Metadata
Assignees
Labels
>enhancementEnhancement of existing functionalityEnhancement of existing functionalitydiscussWe need to figure this outWe need to figure this out