/explore
|
You are here 
|
actuated.dev | ||
| | | | |
blog.alexellis.io
I saw an opportunity to fix self-hosted runners for GitHub Actions. Actuated is now in pilot and aims to solve most if not all of the friction. |
|
| | | | | ||
| | | | |
actuated.com
GitHub warns against using self-hosted Actions runners for public repositories - but why? And are there alternatives? |
|
| | | | | ||
| | | | |
www.styra.com
Build a solid understanding of how to secure Kubernetes along with some best practices. Learn how to secure nodes, clusters and pods. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
