You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 15, 2022. It is now read-only.
Purpose of this feature is to discover possible interop between draft / kd / koding. In order to have a shot at it, we may want first to make it possible to install draftd / helm on k8s cluster built by koding.
Prerequisite list to get there:
kloud/stack: add API for deploying klient on an existing vm (for connecting k8s cluster nodes)
kloud/stack: inject kloud keys per credential (via cloud-init)
kloud/provider: plan API for k8s nodes
kloud/provider: augmentation for cluster resources
@rjeczalik did you have time to work on this? any code to share?
I was planning to assign @protatremy from my team to work on it. We probably were not as ambitious as this plan though.
We were planning to start from the marathon backend, and see how we can make it work on k8s.
Then gradually improve on making it right.
Purpose of this feature is to discover possible interop between draft / kd / koding. In order to have a shot at it, we may want first to make it possible to install draftd / helm on k8s cluster built by koding.
Prerequisite list to get there:
The text was updated successfully, but these errors were encountered: