Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Merge Kuber and Kube-eleven #1569

Open
3 tasks
Despire opened this issue Nov 11, 2024 · 0 comments
Open
3 tasks

Feature: Merge Kuber and Kube-eleven #1569

Despire opened this issue Nov 11, 2024 · 0 comments
Labels
feature New feature

Comments

@Despire
Copy link
Contributor

Despire commented Nov 11, 2024

Description

Kube-eleven: This service is responsible for building and destroying Kubernetes clusters.
Kuber: This service performs actions immediately after a Kubernetes cluster has been built, such as patching nodes, deploying longhorn, deleting nodes.

Both of these services directly work on the k8s cluster, These two services are correlated as without a successful pass during the kube-eleven stage, kuber cannot continue. I suggest we merge these two together into a single service.

By merging these two services, we can:

  • maintain one less service overall
  • refactor the code and make it more robust
  • aiming to reduce complexity.

The end result would be to have 5 micro-services in total:

Manager: takes care of scheduling of what tasks are supposed to be done to achieve the desired state.
Builder: completes task from the manager.
Terraformer: builds the infra.
Ansibler: connects the infra.
Kuber+Kube-eleven: Uses the infra to create a working k8s cluster.

Exit criteria

  • Successful integration of Kube-eleven and Kuber.
  • Testing completed for merged functionality.
  • Documentation updated to reflect changes.
@Despire Despire added the feature New feature label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

1 participant