Remove k8s related packages #48
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: GitHub <noreply@github.com>
Signed-off-by: GitHub <noreply@github.com>
Signed-off-by: GitHub <noreply@github.com>
Signed-off-by: GitHub <noreply@github.com>
Signed-off-by: GitHub <noreply@github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As we're in the transition of replacing k3s as a container control plane with the more lightweight Eclipse Kanto Container Management, we're removing all the Kubernetes/k3s related recipes from the Leda metalayer.
We are aware that this is a breaking change of the metalayer.
However, we've been looking for an "automotive-grade", lightweight alternative to k3s and couldn't find anything. Hence we're making this decision now as early as possible and will focus on containerd-based container runtimes for the Eclipse Leda SDV stack.
We may add support for other container runtime (such as northstar) in the future, but it became clear that the Kubernetes behaviour and system requirements etc. do not quiet fit to our in-vehicle edge stack needs.
For the existing release branches (kirkstone and honister), we'll try to keep them as is, and focus our development on the main branch.