How svtechnmaa/charts works
SVTECH_Public_Helmchart is a catalog of Helm subcharts used as building blocks in SVTECH stack solutions and published through ArtifactHub. The principal workflow is for a stack operator to select a chart, deploy it with Helm to Kubernetes, and use the resulting service. The repository spans application, data, and infrastructure charts; the README names Grafana, Icinga2, and Rundeck and stack examples such as ELK and TACGUI. The Icinga2 election script shows Lease-based leader promotion and reload behavior; wiring among other charts is not established by the sampled source.
Main entry points: election.py Leader election · icinga2 Icinga2 · artifacthub Chart packages · kubernetes Helm chart catalog
Components 23
Chart catalog
- Helm chart catalog
kubernetes - Chart packages
artifacthub
Applications
Data platform
- Elasticsearch
kubernetes/elasticsearch - Kafka
kubernetes/kafka - ClickHouse
kubernetes/clickhouse - PostgreSQL HA
kubernetes/postgresql-ha
Operations
- Icinga2
kubernetes/icinga2 - Leader election
kubernetes/icinga2/files/scripts/election.py - Juniper syslog API
kubernetes/juniper-syslog-api - Topology tools
kubernetes/topology-app
Other components
- Stack operator
- Helm deployment
- Kubernetes cluster
- ArtifactHub
- Kubernetes Lease
- Local Icinga API
- Syncthing
Connections 22
- Stack operator → Helm deployment: selects and deploys
- Helm deployment → Helm chart catalog: uses charts
- Helm deployment → Kubernetes cluster: installs resources
- Stack operator → ArtifactHub: discovers charts
- Chart packages → ArtifactHub: published to
- Kubernetes cluster → Grafana: runs
- Kubernetes cluster → Rundeck: runs
- Kubernetes cluster → TACGUI: runs
- Kubernetes cluster → NetForge services: runs
- Kubernetes cluster → Icinga2: runs
- Kubernetes cluster → Juniper syslog API: runs
- Kubernetes cluster → Topology tools: runs
- Kubernetes cluster → Airflow: runs
- Kubernetes cluster → Mage AI: runs
- Kubernetes cluster → Elasticsearch: runs
- Kubernetes cluster → Kafka: runs
- Kubernetes cluster → ClickHouse: runs
- Kubernetes cluster → PostgreSQL HA: runs
- Icinga2 → Leader election: runs election client
- Leader election → Kubernetes Lease: reads and updates
- Leader election → Syncthing: checks populated config
- Leader election → Local Icinga API: requests reload