Automated Deployments with GitHub and a Private Container Registry
Many teams rely on GitHub Actions and public container registries.
But for sensitive data, research, and safety-critical applications, more is needed: control, security, and data sovereigntyData sovereignty is full control over where your data lives, who accesses it, and how it's used. Learn more →.
The TU Graz Racing Team develops high-performance telemetry and analytics software in Rust.
The code continues to be hosted on GitHub – a platform switch is currently not possible.
At the same time, the team wanted a controlled, auditable releaseA release is the moment when a new feature becomes visible to users. Learn more → process on its own infrastructure – especially for production-related deploymentsDeployment is the moment software goes live. Learn more →.
Architecture: GitHub Build, Automated KubernetesKubernetes is a system for managing containerized applications – automated, scalable, and fault-tolerant. Learn more → Deployment
We provided a container registry into which the team pushes images with specific tags (staging, production).
These tags serve as explicit release triggersA release is the moment when a new feature becomes visible to users. Learn more →.
Our infrastructure detects new tags and automatically rolls them out to the corresponding Kubernetes environmentSoftware environments allow new features to be developed, tested, and deployed safely – in a structured way. Learn more →.
- Build & Push: The team publishes a container image with a tag in the registry (e.g.,
production) - Trigger: The infrastructure detects the tag as a trigger
- Deployment: The image is automatically deployed to the production Kubernetes cluster
All build logic remains on GitHub – operations and deployments are handled by RiKuWe, with full control and traceability.
Benefits for Research-Oriented & Safety-Critical Projects
- CI/CDCI/CD stands for automated software delivery – secure, reproducible, and fast. Learn more → with a clear separation of roles: development on GitHub, operations at RiKuWe
- No dependency on external deployment providers
- Data sovereigntyData sovereignty is full control over where your data lives, who accesses it, and how it's used. Learn more → and GDPR compliance
- Release processes with versioningVersioning makes changes identifiable and traceable – in code, infrastructure, and operations. Learn more → & rollbackA rollback is a controlled step backward – not out of fear, but out of responsibility. Learn more →
- Ideal for sensitive or academic projects with special requirements
Read the Full Case Study
Real-Time Telemetry for the TU Graz Racing Team