Source: medium.com
Installing (EFK) Stack in KubernetesCategory: Software, Kubernetes, yaml
One well-liked centralized solution is that the Elasticsearch, Fluentd, and Kibana (EFK) stack.Elasticsearch could be a period, distributed, and scalable computer program that permits for full-text and structured search, further as analytics.
Step 1 — Creating a NamespaceSo once we tend to begin with Creating cluster , we want to form namespace wherever we are going to have our work directionsTo start , we want to 1st see the present Namespaces in our existing cluster kubectl: Then we must always see the subsequent 3 Namespaces, which require to be pre implemented together with your K8s cluster: So to make the kube-log Namespace we’ll initial open and edit a file known as `kube-log.yaml `using nano or VI:Inside our editor, we’ll paste the desired Namespace object YAML: Then, save and close the file. Once we tend to have created the kube-log.yaml Namespace object file, we’d like produce the Namespace with kubectl create with the -f filename flag: We should see the subsequent output: we can then ensure that the Namespace was created: Now, we should always see the new kube-log Namespace: We can now deploy an Elasticsearch cluster here
Finally, we have a tendency to set Kibana’s instrumentation port to 5601, to that the kibana Service can forward requests.
We can currently check Kibana to verify that log information or data is being properly collected and shipped to Elasticsearch.
Step 1 — Creating a NamespaceSo once we tend to begin with Creating cluster , we want to form namespace wherever we are going to have our work directionsTo start , we want to 1st see the present Namespaces in our existing cluster kubectl: Then we must always see the subsequent 3 Namespaces, which require to be pre implemented together with your K8s cluster: So to make the kube-log Namespace we’ll initial open and edit a file known as `kube-log.yaml `using nano or VI:Inside our editor, we’ll paste the desired Namespace object YAML: Then, save and close the file. Once we tend to have created the kube-log.yaml Namespace object file, we’d like produce the Namespace with kubectl create with the -f filename flag: We should see the subsequent output: we can then ensure that the Namespace was created: Now, we should always see the new kube-log Namespace: We can now deploy an Elasticsearch cluster here
Finally, we have a tendency to set Kibana’s instrumentation port to 5601, to that the kibana Service can forward requests.
We can currently check Kibana to verify that log information or data is being properly collected and shipped to Elasticsearch.
Related Articles
Community Partners
DevOps Careers