...
and modify the lines highlighted by the comments in the following extract (: if the cluster and the VM that collects the data share the same subnet, you can also use the internal IP of the VM instead of the FIP; to allow the creation of Pods also on the master, add the lines shown at the bottom).
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
output.elasticsearch:
hosts:['${ELASTICSEARCH_HOST:elasticsearch}:${ELASTICSEARCH_PORT:9200}'] # <--- Enter the desired port
username: ${ELASTICSEARCH_USERNAME}
password: ${ELASTICSEARCH_PASSWORD}
-----------------------------------------------------
env:
name: ELASTICSEARCH_HOST
value: <FIP><IP> # <--- Enter the Floating/Internal IP of the host FIP with elasticsearch
name: ELASTICSEARCH_PORT
value: "9200" # <--- Enter the port (like above)
name: ELASTICSEARCH_USERNAME
value: elastic
name: ELASTICSEARCH_PASSWORD
value: changeme
name: ELASTIC_CLOUD_ID
value:
name: ELASTIC_CLOUD_AUTH
value:
name: NODE_NAME
-----------------------------------------------------
# this toleration is to have the daemonset runnable on master nodes. Remove it if your masters can't run pods
spec:
template:
spec:
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule |
...