https://github.com/thatmlopsguy/dokaseca-portal
GitOps Configuration and documentation of my Kubernetes homelab powered by ArgoCD
https://github.com/thatmlopsguy/dokaseca-portal
backstage devops dokaseca gitops platform-engineering
Last synced: 2 months ago
JSON representation
GitOps Configuration and documentation of my Kubernetes homelab powered by ArgoCD
- Host: GitHub
- URL: https://github.com/thatmlopsguy/dokaseca-portal
- Owner: thatmlopsguy
- License: apache-2.0
- Created: 2026-02-11T20:39:48.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-02-16T21:19:21.000Z (4 months ago)
- Last Synced: 2026-02-17T02:58:56.201Z (4 months ago)
- Topics: backstage, devops, dokaseca, gitops, platform-engineering
- Homepage: https://thatmlopsguy.github.io/dokaseca-control-plane/
- Size: 13.7 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# Doka Seca Backstage Portal

*Just as ships are built in dry docks, platforms are crafted in DoKa Seca*
>⚠️ Note
>
> DoKa Seca is still in relatively early development. At this time, **do not use** Doka Seca for critical production systems.
## 👋 Introduction
Welcome to **DoKa Seca** - Distributed Orchestration Kubernetes Automation with Scalable Edge Computing Applications - a comprehensive framework for bootstrapping cloud-native platforms using Kubernetes in Docker (Kind)!
The name "DoKa Seca" is a playful Portuguese phrase where "DoKa" incorporates the "K" from Kubernetes (representing the containerized orchestration at the heart of this project), and "Seca" means "dry" - drawing inspiration from the concept of a **dry dock**. Just as ships are built, repaired, and maintained in dry docks - controlled, isolated environments where all the necessary infrastructure and tooling are readily available - DoKa Seca provides a "dry dock" for Kubernetes platforms. It creates an isolated, controlled environment where entire cloud-native platforms can be rapidly assembled, configured, and tested before being deployed to production waters.
DoKa Seca provides an opinionated, production-ready framework that automates the entire platform bootstrap process using Kind clusters. Rather than just being a collection of configurations, it's a complete platform engineering solution that provisions infrastructure, installs essential tooling, configures GitOps workflows, and sets up observability - all with a single command, in your local "dry dock" environment.
This project serves as both a personal learning journey into modern DevOps practices and a comprehensive resource for platform engineers and developers interested in rapidly spinning up production-grade Kubernetes environments. Here you'll find real-world implementations of GitOps workflows, infrastructure as code, observability stacks, and cloud-native security practices - all designed to run efficiently in local development or homelab environments while following enterprise-grade patterns and best practices.
DoKa Seca consists of 5 GitHub repositories:
| Repository | Description |
|------------------------------------------------------------------------------------|-----------------------------------------------------|
| [dokaseca-control-plane](https://github.com/thatmlopsguy/dokaseca-control-plane) | Control plane infrastructure and cluster management |
| [dokaseca-addons](https://github.com/thatmlopsguy/dokaseca-addons) | Platform addons and Kubernetes extensions |
| [dokaseca-workloads](https://github.com/thatmlopsguy/dokaseca-workloads) | Application workloads and deployments |
| [dokaseca-portal](https://github.com/thatmlopsguy/dokaseca-portal) | Backstage project (TBD) (optional) |
| [dokaseca-portal-catalog](https://github.com/thatmlopsguy/dokaseca-portal-catalog) | Backstage Catalog (TBD) (optional) |
This repository, **dokaseca-portal**, is intended to serve as the home for the Backstage portal implementation. The goal is to create a user-friendly interface that provides insights into the platform's state, allows for easy access to documentation, and serves as a central hub for developers and platform engineers interacting with the DoKa Seca environment.