k8s-claimer
k8s-claimer copied to clipboard
A leasing system for a pool of Kubernetes clusters
Requires #6, #7 and #8 After [CreateLease](https://github.com/deis/k8s-claimer/issues/7) and [DeleteLease](https://github.com/deis/k8s-claimer/issues/8) are implemented, the server should be able to create new clusters and lease them out (atomically) according to some configuration. See...
(It doesn't look like we are doing so yet...)
#52 implements a crude-but-functional authentication mechanism to fix #17. We did this because we wanted to get _some_ kind of security (even if not complete) into the server. #52 still...
This endpoint should return the current lease status of all clusters. One possible response: ``` json { "CLUSTER_NAME": { "leased": true, "time_left": "NUM_SECONDS_LEFT_ON_LEASE", "lease_expiration_time": "LEASE_EXPIRATION_TIME_IN_RFC3339" }, "OTHER_CLUSTER_NAME": { "leased": false,...
#48 introduced namespace cleanup on a k8s cluster, but we should perform any deletions concurrently.
This issue is a continuation of https://github.com/deis/k8s-claimer/pull/10#issuecomment-205885692, and requires that identities be added to the leaser for each lease. Since each lease already has the following key/value pair in a...