- Join/Create k8s cluster as master and or worker by introducing host, id and hash information to VyOS configuration
- Utilize existing podman integration to drive cluster’s work
- On masters integrate kubectl tool
- Find proper CNI implementation for VyOS swarm usecase
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Config syntax change (migratable)
- Issue type
- Feature (new functionality)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Not Applicable | FEATURE REQUEST | None | T5380 VyOS Kubelet (k8s) | ||
| Not Applicable | FEATURE REQUEST | None | T5381 Extend VyOS Configuration for joining kubelet service | ||
| Not Applicable | FEATURE REQUEST | None | T5382 Integrate kubeadm and kubectl | ||
| Not Applicable | FEATURE REQUEST | None | T5383 Extend VyOS Configuration for initializing kubelet service | ||
| Not Applicable | FEATURE REQUEST | None | T5384 Integrate proper CNI integrating or at least not conflicting with VyOS |
Event Timeline
Comment Actions
- I want to have something like minikube on my VyOS router joining my k8s with my services so data is replicated and I can "balance" the services to my home.
- Coming from my R&D journey of https://causal-rt.org I'm trying to further rethink a few things including social networking, one goal would be to get a communication service for "convergent/consent-forging human swarm interaction" https://dory-swarm.org onto the edge, rather than relying on central or semi-decentral services for relaying communication.