Repository metrics
- Stars
- (983 stars)
- PR merge metrics
- (PR metrics pending)
Description
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.