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

Create documentation (matrix) outlining diffs to vanilla k8s #272

Open
anilmurty opened this issue Oct 30, 2023 · 0 comments
Open

Create documentation (matrix) outlining diffs to vanilla k8s #272

anilmurty opened this issue Oct 30, 2023 · 0 comments
Assignees

Comments

@anilmurty
Copy link

anilmurty commented Oct 30, 2023

It will be useful to have a matrix that lists out features that are supported in plain/ vanilla Kubernetes but not supported or limitedly supported in Akash. This will be useful for multiple reasons:

  1. Having a ready reference for any users/ customers/ providers, when the questions come up, would reduce support burden and distractions.
  2. Would be helpful for customers running workoads in k8s and wanting to migrate to Akash (particularly as we look to attract AI training workloads that may be running in AKS, EKS, GKE or ray+k8s)
  3. Would help us prioritize feature work taking into account these limitations, so that we're making it easier for folks to adopt Akash.

Here's what I am suggesting:

  1. A note about the version of K8s and the version of Akash where this was last updated.
  2. A matrix style document that has a list of features that are either not supported or supported in a limited capacity in column 1.
    Column 2 is whether there is support, no support or limited support in Akash
    Column 3 is some notes on why the feature isn't currently supported
    Column 4: reference to any issues created for it in the backlog, if they exist.

Eg:

K8s Feature Akash State Notes Reason Github reference (if applicable)
Shared persistent storage volumes Not supported If a SDL defines a single profile with a persistent storage definition - and that profile is then used by multiple services - individual, unique volumes will be created per service.
Multiple persistent storage volumes per service Not supported only a single persistent volume is allowed/supported per service definition in the Akash SDL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog (not prioritized)
Development

No branches or pull requests

2 participants