Skip to content

Kusama network alerting in Prometheus/Kubernetes using Wireguard VPN

Notifications You must be signed in to change notification settings

taggelos/kusama-watcher

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

kusama-watcher 🐦

Information about the scope of the project can be found in https://gist.github.com/ironoa/40ee9e291b29c5af26d78ab238889edd

Working environment

  • CentOS Linux release 7.9.2009 (Core)
  • Kubernetes version 1.21.1
  • Docker version 20.10.6, API Version 1.41
  • Helm v3.1.1
  • Wireguard v1.0.20210424

Opensource Projects used



main branch

You need to set the environment variables for the server port and the validators list by using source env_vars
Run the program using yarn && yarn build && yarn start
Use docker build -t ksm-watcher . --network=host to build the docker image.

helmChartBranch branch

Here you can find the helmChart created for this application under kusamaHelmChart folder.
This branch also consists of the values.yaml changes on the kube-prometheus-stack chart.
Trigger the Helm chart installation/upgrade by configuring the values.yaml and running inside the folder:
helm upgrade ksm-watcher . -f values.yaml

wireguard branch

For this branch we need to set our wireguard connection between 2 machines.
In my case I had the kubernetes cluster with the prometheus instances and the application running in docker in another machine.
In order to set your wireguard connection you can use the following guide.
This process can be automated as well.
In this branch there are the resources for kubernetes to communicate using the wg0 interface to the application on the other side.
You can deploy them using helm upgrade wireguard . -f values.yaml

About

Kusama network alerting in Prometheus/Kubernetes using Wireguard VPN

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published