Skip to main content

K1s Roadmap

K1s roadmap is a list of Kubernetes features that are planned to be implemented in the future and what features we are working with now. Keep in mind that the roadmap is not a promise to implement the features. The roadmap is subject to change, and the features may be removed or added at any time. Keep an eye on the roadmap to see what features we are working on.

SymbolDescription
Done
👷🏽‍Under Construction
Planned, coming next
-Not plan yet
🚫Not supported
Get Early Access!

Get the early access to our Serverless Kubernetes platform and get the latest updates on the implementation progress.
Register here

K1s Serverless API Dashboard


PATHStatusgetcreatedescribepatchdeleteput
/api/-----
/api/v1/-----
/apis/-----
/apis/apps-----
/apis/apps/v1-----
/api/v1/pods-----
/api/v1/namespaces----
/api/v1/namespaces/{name}👷--
/api/v1/namespaces/{name}/pods👷👷---

The Kubernetes API is huge with 428 API endpoints (paths), 113 for api group and 310 for apis group endpoints! We are working on the API dashboard to make it easier to navigate the API endpoints and the status on each of these.

K1s Terminal Roadmap

kubectl

In summary, this roadmap is the list of features that we are planning to implement first. The roadmap is subject to change, and the features may be removed or added at any time. Keep an eye on the roadmap to see what features we are working on.

kubectl api-resources -owide | grep all
NAMESHORTNAMESAPIVERSIONNAMESPACEDKINDVERBS
podspov1truePodcreate,delete,deletecollection,get,list,patch,update,watch
replicationcontrollersrcv1trueReplicationControllercreate,delete,deletecollection,get,list,patch,update,watch
servicessvcv1trueServicecreate,delete,deletecollection,get,list,patch,update,watch
daemonsetsdsapps/v1trueDaemonSetcreate,delete,deletecollection,get,list,patch,update,watch
deploymentsdeployapps/v1trueDeploymentcreate,delete,deletecollection,get,list,patch,update,watch
replicasetsrsapps/v1trueReplicaSetcreate,delete,deletecollection,get,list,patch,update,watch
statefulsetsstsapps/v1trueStatefulSetcreate,delete,deletecollection,get,list,patch,update,watch
horizontalpodautoscalershpaautoscaling/v2trueHorizontalPodAutoscalercreate,delete,deletecollection,get,list,patch,update,watch
cronjobscjbatch/v1trueCronJobcreate,delete,deletecollection,get,list,patch,update,watch
jobs-batch/v1trueJobcreate,delete,deletecollection,get,list,patch,update,watch

Core API Group

kubectl api-resources --api-group='' -owide
ResourceKindStatusgetlistwatchcreateupdatepatchdeletedeletecollection
podsPod👷-------
namespacesNamespace👷------🚫
configmapsConfigMap---------
endpointsEndpoints---------
eventsEvent---------
limitrangesLimitRange---------
nodesNode---------
persistentvolumeclaimsPersistentVolumeClaim
persistentvolumesPersistentVolume---------
podtemplatesPodTemplate---------
replicationcontrollersReplicationController---------
resourcequotasResourceQuota---------
secrets----------
serviceaccountsServiceAccount---------
servicesService---------
bindings--🚫🚫🚫-🚫🚫🚫🚫
componentstatusesComponentStatus---🚫🚫🚫🚫🚫🚫

API Groups within all flag

Which resources are available in the all API group?

kubectl api-resources -owide | grep all

Only the following resources are available in the all API group that are NOT in the core API group:

ResourceKindStatusgetlistwatchcreateupdatepatchdeletedeletecollection
replicationcontrollersReplicationController---------
servicesService---------
daemonsetsDaemonSet---------
deploymentsDeployment---------
replicasetsReplicaSet---------
statefulsetsStatefulSet---------
horizontalpodautoscalersHorizontalPodAutoscaler---------
cronjobsCronJob---------
jobsJob---------

Plan based on Kubernetes API Verbs

The all keyword in Kubernetes is a special keyword that represents all resources. When you use kubectl with all, it performs the operation on "all resources that it supports".

For example, if you run kubectl get all, it will return all resources that it supports, such as pods, services, deployments, and so on.

However, it's important to note that all does not truly select absolutely all resources in Kubernetes. It only selects resources that are most commonly used by end-users and are expected to be viewed together.

Hence, it is worth to start the k1s' kubectl implementation of the resources based on the Kubernetes Resource and Verbs, irrespective of the API group.

  • kubectl get {} command
  • kubectl create {} command
  • kubectl delete {} command
  • kubectl patch {} command
  • kubectl update {} command
  • kubectl watch {} command

Variants to consider:

  • kubectl get {} --all-namespaces command
  • kubectl get {} [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file|custom-columns|custom-columns-file|wide] (TYPE[.VERSION][.GROUP] [NAME | -l label] | TYPE[.VERSION][.GROUP]/NAME ...) [flags] [options] command
  • kubectl delete ([-f FILENAME] | [-k DIRECTORY] | TYPE [(NAME | -l label | --all)]) [options] command

Subscribe

Subscribe to our newsletter to get the latest updates on the implementation progress.


By continuing you agree to our

Privacy Policy