Explore >> Select a destination
|
You are here 
|
developer-friendly.blog | ||
| | | | |
nikdoof.com
|
|
| | | | | For some time, I've been using a Zig-a-zig-ah and Zigbee2MQTT on a spare Raspberry Pi 2. It was far from the most stable platform as the zzh sucked power and caused voltage issues with the Pi, but it worked for what I needed. After a few months, I was frustrated at the frequent restarts the system required. The voltage drops should cause just enough of an issue for Z2M to stop communicating with the zzh and break all of my home automation. | |
| | | | |
nikdoof.com
|
|
| | | | | vCluster is a great tool for anyone managing larger Kubernetes clusters which may contain multiple users, environments, a need for larger isolation between workloads. For me vCluster works brilliantly as a method of testing new applications in a disposable cluster where I can run some of the larger, more integrated operators and tooling without much fear of interfering with my existing Kubernetes setup. In my cluster I make use of Flux to manage my manifest and resources in a GitOps method, and using vCluster with Flux and a dash of OIDC makes for an excellent user experience. | |
| | | | |
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. | |
| | | | |
heltweg.org
|
|
| | | Kubernetes for sideprojects: Hardware is dead | ||
