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 sovereignty.

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 release process on its own infrastructure – especially for production-related deployments.

Architecture: GitHub Build, Automated Kubernetes Deployment​

We provided a container registry into which the team pushes images with specific tags (staging, production).
These tags serve as explicit release triggers.

Our infrastructure detects new tags and automatically rolls them out to the corresponding Kubernetes environment.

1. Build & Push: The team publishes a container image with a tag in the registry (e.g., production)
2. Trigger: The infrastructure detects the tag as a trigger
3. 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/CD with a clear separation of roles: development on GitHub, operations at RiKuWe
• No dependency on external deployment providers
• Data sovereignty and GDPR compliance
• Release processes with versioning & rollback
• Ideal for sensitive or academic projects with special requirements

Read the Full Case Study​

Real-Time Telemetry for the TU Graz Racing Team

Related Content​

• CI/CD as a Service at RiKuWe
• Container Registry as a Service
• Managed Kubernetes Clusters