Helm logging system deployment EFK

EFK department --- Elasticsearch + Fluentd + Kibana
# Helm fetch stable / elasticsearch # value can be modified according to the value of their needs may not modify 
# helm install --name els --namespace = efk -f values.yaml stable / elasticsearch # we can assign values to use the -f .yaml

# Kubectl run cirror- $ RANDOM --rm -it --image = cirros - / bin / sh # cirros can quickly build a java client
# curl ELS-elasticsearch-client.efk.svc.cluster.local: 9200
# client.efk.svc.cluster.local elasticsearch-ELS-curl: 9200 / _cat / Nodes

# fETCH Helm the stable / fluentd pull-elasticsearch # fluentd, modify the value value.yaml in elasticsearch the host, host after deployment elasticsearch parsed the domain
log ♦ If you need to collect the master node, you need to modify tolerations, compatible with the master node stain; if fluents prometheus need to be monitored, it is necessary to open the annotations; if you need to access the service through the need to open the service

# Helm install Flu --namespace --name = -f values.yaml the stable eFK / fluentd-elasticsearch
# curl-ELS-elasticsearch client.efk.svc.cluster.local: 9200 / _cat / indecis

# FETCH Helm the stable / kibana # elasticsearch modification in the host value.yaml value, host to resolve the post-deployment elasticsearch domain; convenient external access Service type amended as NodePort
# helm install --name kib --namespace=efk -f values.yaml stable/kibana

 

Guess you like

Origin www.cnblogs.com/alamisu/p/11355058.html
efk