Raspberry Pi K3s Cluster

This page summarizes the projects mentioned and recommended in the original post on dev.to

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • raspberian-firstboot

    A lightly modified Raspbian-light image supporting first boot customization.

  • The first problem I didn't want to deal with manually was configuring the ssh on the RPis. In the previous process, I had one playbook to configure the ssh and user on Raspberian and another to configure everything else. This time, though, the node will boot with password login disabled and with my public keys automatically added to the host. To achieve this, I used Raspberian Firstboot with a custom script to set up the ssh configuration and hostname.

  • rpi-cluster

    My automated raspberry pi k3s setup

  • The first problem I didn't want to deal with manually was configuring the ssh on the RPis. In the previous process, I had one playbook to configure the ssh and user on Raspberian and another to configure everything else. This time, though, the node will boot with password login disabled and with my public keys automatically added to the host. To achieve this, I used Raspberian Firstboot with a custom script to set up the ssh configuration and hostname.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • sealed-secrets

    A Kubernetes controller and tool for one-way encrypted Secrets

  • My first approach to keeping secrets versioned was using Sealed Secrets. However, I gave up on the sealed secrets because I rebuilt the cluster frequently and always lost the encryption keys since I didn't care to make backups. I found it a lot easier to keep an encrypted secrets.yaml file in the repository. Every time I spin up a new cluster in this workflow, I have to decrypt the file and apply it to the new cluster. Although it is encrypted, I don't recommend keeping the file in a public Github repository. I'm doing this to avoid losing the secrets while I work out a better flow for personal projects.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Plain text Kubernetes secrets are fine

    1 project | news.ycombinator.com | 21 Jul 2023
  • Weekly: Questions and advice

    1 project | /r/kubernetes | 18 Apr 2023
  • 3rd part secret storage

    1 project | /r/ansible | 10 Dec 2022
  • Management of kubernetes secrets - best practices?

    1 project | /r/kubernetes | 6 Dec 2022
  • Usage of rails credentials mechanism

    1 project | /r/rails | 6 May 2022