https://github.com/shadowjonathan/kaas
[WIP] Kubernetes-as-a-service, also: dutch for 'cheese'
https://github.com/shadowjonathan/kaas
Last synced: 4 months ago
JSON representation
[WIP] Kubernetes-as-a-service, also: dutch for 'cheese'
- Host: GitHub
- URL: https://github.com/shadowjonathan/kaas
- Owner: ShadowJonathan
- License: gpl-3.0
- Created: 2020-06-01T12:36:10.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2020-06-01T15:41:49.000Z (about 6 years ago)
- Last Synced: 2025-09-12T01:18:13.529Z (9 months ago)
- Size: 18.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# `kaas`
"kaas": noun
1. Multi-tenant Multi-Cluster Kubernetes-as-a-Service
2. *(dutch)* "Cheese"
**This repository is a WIP, i'll plan to start working on this sometime in the future, using projects from [multi-tenancy](https://github.com/kubernetes-sigs/multi-tenancy) and [submariner](https://submariner.io/) to make this happen**
# The Goal
Provide a simple dashboard admin GUI (with CLI feature pairing) for sysadmins/devops to provision and provide virtual clusters to internal teams and business customers alike.
Define resource pools (Loadbalancer IPs, ingress subdomain patterns, storage classes, etc.) and limits to be used by Tenant clusters in an intuitive and easy way (think DigitalOcean dashboard).
Provide mission-agnostic functions/features that can serve:
- professional usecases (commercial & internal)
- hobbyist collaberative usecases (collaberative clustering, providing compute resources from a local homelab cluster to a wider community, etc.)
- conventional abstract usecases (seperating a "personal" and "work" kubernetes cluster while using the same hardware)
Provide a structure layer that can dynamically lease and release clusters (as they get provisioned or (taken) down) while still maintaining high availibility / redundancy for many tenants; divorce the resource owner and it's user even further.