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
which makes me think it's already prepared to be extensible for other drivers than docker+etcd.
Thinking of a possible implementation, there are many ways to do it in Kubernetes. I'd think the most "kubernetes way" would be to add a driver that replaces Docker calls with Kubernetes calls and use Kubernete's CRDs as a storage means instead of etcd.
The text was updated successfully, but these errors were encountered:
Yeah, it is not tightly coupled with docker. there is an interface that has the needed functionality for k8s implementation (https://github.com/Clivern/Peanut/blob/main/core/runtime/base.go#L8-L11). tbh i am not sure when i will support k8s since i care about the command line first and there will a lot to do to support k8s.
Anyways here is how i see it:
Peanut can run outside the k8s cluster & uses the kube config to create/modify deployments, services and configmaps.
and it can be deployed inside the cluster and have service account to be able to create/modify deployments, services and configmaps from inside the cluster.
Is having a Kubernetes driver something on the roadmap for this project? I'm exploring the possibilities here, not really requesting a feature 馃檪
I noticed the code contains something like:
which makes me think it's already prepared to be extensible for other drivers than docker+etcd.
Thinking of a possible implementation, there are many ways to do it in Kubernetes. I'd think the most "kubernetes way" would be to add a driver that replaces Docker calls with Kubernetes calls and use Kubernete's CRDs as a storage means instead of etcd.
The text was updated successfully, but these errors were encountered: