/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 actuated.com
Secure CI for GitLab with Firecracker microVMs
| | actuated.dev
Is the GitHub Actions self-hosted runner safe for Open Source?
1.1 parsecs away

Travel
| | GitHub warns against using self-hosted Actions runners for public repositories - but why? And are there alternatives?
| | actuated.dev
Introducing burst billing and capacity for GitHub Actions
1.4 parsecs away

Travel
| | Actuated now offers burst billing and capacity for customers with spiky and unpredictable CI/CD workloads.
| | blog.alexellis.io
Blazing fast CI with MicroVMs
0.7 parsecs away

Travel
| | 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.
| | arveknudsen.com
Installing Elasticsearch/Kibana 5.5 within Kubernetes cluster on AWS | Arve Knudsen's Blog
13.4 parsecs away

Travel
| 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.