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

[Concept] : [Kube] : Elemental Worker Deployment #2674

Open
h0lybyte opened this issue Sep 6, 2024 · 6 comments
Open

[Concept] : [Kube] : Elemental Worker Deployment #2674

h0lybyte opened this issue Sep 6, 2024 · 6 comments
Assignees
Labels
0 Neutral Level todo This issue is slated for progression.

Comments

@h0lybyte
Copy link
Member

h0lybyte commented Sep 6, 2024

Core Concept/Theory
A clear and concise description of what the concept is. Ex. It would be cool if [...]

Deploying a k3s worker node on the openSUSE MicroOS operating system
MicroOS, a minimal and immutable operating system designed for containerized workloads, offers an ideal environment for lightweight k3s workers. The concept here is to explore and document the steps required to deploy k3s worker nodes on MicroOS, leveraging its robust security and transactional updates to support Kubernetes edge workloads. This deployment would enhance cluster stability and provide a streamlined, secure, and automated OS for the worker nodes.


Alternative Ideas
Is there any other way this concept could be used?

Yes, MicroOS’s lightweight and immutable architecture could also be beneficial for other edge computing use cases beyond Kubernetes, such as IoT or distributed container systems where security and simplicity are critical. It may also be tested with other container orchestration tools like Docker Swarm, Rancher, or Nomad.


Alternative Examples/Sources
Are there any other references that you can provide?


Additional information
Add any other context or examples of this concept here.

One important aspect to consider is MicroOS's automatic rollback feature, which provides system snapshots and ensures quick recovery in case of failure. This feature will be essential in ensuring that edge worker nodes can automatically recover from OS-level failures without manual intervention, thus maintaining uptime for critical workloads. Also, Longhorn for persistent storage can be used with this setup to persist data across nodes.

@h0lybyte h0lybyte added 0 Neutral Level enhancement New feature or request labels Sep 6, 2024
@h0lybyte h0lybyte self-assigned this Sep 6, 2024
@h0lybyte h0lybyte added this to KBVE Sep 6, 2024
@h0lybyte h0lybyte moved this to Theory in KBVE Sep 6, 2024
@h0lybyte
Copy link
Member Author

h0lybyte commented Sep 6, 2024

We can deploy this image using a terraform script through github actions, making it a bit easier for us to deploy new images and workers in the future.

Now I am debating if we want to set it up so that it gets deployed via terraform directly from a workflow or an issue comment.

@h0lybyte
Copy link
Member Author

@h0lybyte h0lybyte added backlog This issue is postpone. and removed enhancement New feature or request labels Nov 10, 2024
@h0lybyte h0lybyte moved this from Theory to Backlog in KBVE Nov 10, 2024
@h0lybyte
Copy link
Member Author

Currently backlogged until we expand the VMs again or have more space to experiment.

@h0lybyte
Copy link
Member Author

@h0lybyte h0lybyte moved this from Backlog to Todo in KBVE Dec 19, 2024
@h0lybyte h0lybyte moved this from Todo to Backlog in KBVE Dec 19, 2024
@h0lybyte h0lybyte added todo This issue is slated for progression. and removed backlog This issue is postpone. labels Dec 19, 2024
@h0lybyte h0lybyte moved this from Backlog to Todo in KBVE Dec 19, 2024
@h0lybyte h0lybyte changed the title [Concept] : [Kube] : MicroOS Worker Deployment [Concept] : [Kube] : Elemental Worker Deployment Dec 19, 2024
@h0lybyte
Copy link
Member Author

elemental-architecture-v1 5

@h0lybyte
Copy link
Member Author

Elemental operator is deployed but we still need to add a couple workers using it.
Once we get two up and running, I will close this issue ticket out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 Neutral Level todo This issue is slated for progression.
Projects
Status: Todo
Development

No branches or pull requests

1 participant