Repository to host projects under Kubernetes Development
  • Perl 95.1%
  • Python 4%
  • Java 0.6%
  • Dockerfile 0.2%
Find a file
2025-12-09 11:05:33 -08:00
alerttally Merge branch 'main' into alerttally-ui 2025-12-09 10:53:47 -08:00
clientmachine Merge branch 'main' into flinkRESTapi 2025-12-09 10:58:42 -08:00
flink Merge branch 'main' into mrui 2025-12-09 10:59:23 -08:00
graylog Changed zmq stream data source to comply with pipeline field to separate data streams. 2025-10-22 11:04:53 -07:00
kubernetesadmin Updated haproxy.cfg 2024-06-25 17:28:29 +00:00
linps Merged PR 639: AlertTally refactor and update 2025-08-18 21:20:23 +00:00
reference Merge branch 'main' into flinkRESTapi 2025-12-09 10:58:42 -08:00
.gitignore Adding scaffolding to git repo 2023-07-24 21:43:53 +00:00
README.md Reverting changes to links. 2023-07-31 12:53:52 -07:00

Runbook Kubernetes

The Runbook Kubernetes cluster is resposible for all microservices supporting Runbook.

Important Information

This Kubernetes cluster has several major components:

  1. Haproxy load balancer running on k8savage01 balances requests between the three Kubernetes control planes.
  2. Kubernetes control planes k8savage02, k8savage03, and k8savage04 which manage the entire cluster. All administration or management work is done on these machines.
  3. Kubernetes worker nodes, which will be all further machines added to the cluster. Intent is for k8savage06-k8savage10 to be the initial worker nodes.
  4. Outside resources used by the cluster. As of now k8savage05 hosts a Redis database that holds process data for LinPS and an api that allows access to that data.

Important links

  1. Haproxy Statistics - http://k8savage01.svceng.com:9999/stats
  2. Grafana Charts - http://k8savage01.svceng.com:9010/
  3. Alertmanager - http://k8savage01.svceng.com:9020/
  4. Redis Api to retrieve process data - http://k8savage05.svceng.com:33107/

How to Build/Use this repository

  • This repository has Service (or general topic) name at the top level.
  • Below that will be a directory for containers and another for k8config. (Note kubernetesadmin and clientmachine are special cases)
  • The directory for containers will have a separate directory for each container used in that Service named the same as the container. This directory will contain all of the files necessary to build the container.
  • The directory for k8config will contain a yml file that will contain all information necessary to deploy/delete all pieces of the Service with the command kubectl create/delete -f filename.yml.
  • Directory kubernetesadmin contains configuration files and documentation files about the creation/maintenence/expansion of the Kubernetes cluster.
  • Directory clientmachine contains containers that are meant to be deployed onto client machines and not in the Kubernetes cluster.

Further Information

For further information each directory in this repository will contain additional markdown files for documentation.