Repository navigation
[Enhancement]: Multi Node Enablement #460
Description
Design Document Link
This enhacement is meant to discuss design and architecture decisions to implement a new feature called “Multi-node”.
Currently, MicroShift provides a single node cluster with Kubernetes and OpenShift control plane and node components embedded into a single binary, and some extra services running as scheduled pods. Multi-node should allow users to run MicroShift in multiple devices and work as a single cluster.
Multi-node should be approached from two perspectives:
Multiple worker nodes: provides the ability to add new worker nodes to an existing cluster
Highly available control plane: provides the ability to add new control plane nodes providing control plane workload balancing and high availability.
What would you like to be added:
The ability for MicroShift to create a single cluster out of several devices (multiple worker nodes, and high available control plane)
Why is this needed:
High availability or expanding capacity might be requirements in edge computing scenarios.
This enhacement should be the parent of several tasks that will enable different aspects of the feature.
Activity
oglok commentedon Nov 17, 2021
#461
oglok commentedon Nov 29, 2021
#471
openshift-bot commentedon May 18, 2022
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting
/remove-lifecycle stale.Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting
/lifecycle frozen.If this issue is safe to close now please do so with
/close./lifecycle stale
openshift-bot commentedon Jun 17, 2022
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting
/remove-lifecycle rotten.Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting
/lifecycle frozen.If this issue is safe to close now please do so with
/close./lifecycle rotten
/remove-lifecycle stale
openshift-bot commentedon Jul 17, 2022
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.Mark the issue as fresh by commenting
/remove-lifecycle rotten.Exclude this issue from closing again by commenting
/lifecycle frozen./close
openshift-ci commentedon Jul 17, 2022
@openshift-bot: Closing this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.