Explore >> Select a destination
|
You are here 
|
mherman.org | ||
| | | | |
arveknudsen.com
|
|
| | | | | In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. This is generally known as the ELK stack, which stands for Elasticsearch, Logstash (precursor to Fluentd) and Kibana. | |
| | | | |
hayl.in
|
|
| | | | | [AI summary] The article explains how to use GitHub Actions to build Docker images and trigger Kubernetes deployment rollouts by setting up service accounts and tickets. | |
| | | | |
jb3.dev
|
|
| | | | | AlertManager is a rock solid approach for alerting in Prometheus, but how do you make it highly available on Kubernetes? This article covers my approach to making AlertManager highly available on Kubernetes, and how you can do the same. | |
| | | | |
managing.blue
|
|
| | | [ Yes, headlamp is a better choice for this ] Sometimes when you are working with microk8s, you may want to run the Kubernetes dashboard. We first enable it with microk8s enable dashboard. We assume that we have microk8s enable rbac and microk8s enable metrics-server already. The dashboard pod runs in the kube-system namespace. To... | ||
