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: Kubernetes-Compatible Resource Schema and API #506

Open
dtsulik opened this issue Sep 9, 2023 · 5 comments
Open

Feature: Kubernetes-Compatible Resource Schema and API #506

dtsulik opened this issue Sep 9, 2023 · 5 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@dtsulik
Copy link

dtsulik commented Sep 9, 2023

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
For starters nanocl should be able to consume existing k8s yaml schemas for resources without need for external tool. In the long term, achieving feature parity with k8s will significantly ease adoption. This extends to API as well, it should have same response/request models as k8s. This would allow nanocl to take advantage of existing tools like ArgoCD, OPA and many more.

Describe alternatives you've considered
Alternative to natively supporting processing k8s compatible schemas would be to have some converter tool, which makes migration much more complex process.

Additional context
K8s has incredibly rich ecosystem, nanocl being compatible with them would be huge benefit for the project.

@dtsulik dtsulik added the enhancement New feature or request label Sep 9, 2023
@leon3s
Copy link
Member

leon3s commented Sep 12, 2023

Hey @dtsulik, thanks for your interest in the project !

The main idea behind nanocl is to be a developer tools first and make things simpler than kubernetes.
This is why we don't have the same spec.
Currently maintaining 2 specs will be huge work as i'm alone.
I'll keep the issue open, if the community chooses to follow the kubernetes API, we will, as nanocl is also a community tool.
But i'll prefer to see a rewrite of argoCD for nanocl to be honest, with his virtual machine capability it shouldn't be a big deal.
I wanted to make something similar as github workflows but that run on nanocl.

@waqasraz
Copy link

waqasraz commented Oct 5, 2023

I agree with @dtsulik to keep the same specs as k8s if we want nanocl adoption. Because we know naming is hard in computer science, if we come up with our APIs, most likely, we will make things complex rather than simpler.

@anonkey
Copy link
Contributor

anonkey commented Oct 10, 2023

I think converter tool is the best agreement, but maintain it could be a mess so should be done by someone using k8s and nanocl regularly

@ivanovaleksandar
Copy link

This does not have to be a direct implementation, but a separate opt-in component that and does translations for kubernetes API objects to the nanocl API objects.

@leon3s
Copy link
Member

leon3s commented Dec 11, 2023

A translations tools like we did for docker compose is the solution i would prefer, if anyone with good knowledge of the Kubernetes spec would like to work with me on this, feel free to reach me out on discord or using mail!

@leon3s leon3s added the help wanted Extra attention is needed label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants