Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FeaturesKubeOneKubesprayKindKubeadmOpenShift OriginAirship
Declarative Cluster Configuration - describing the K8s cluster including infra components (eg. CRI, CNI), versions, number of nodes (master+worker), architecture, K8s certificatesYYNNYY. Use Uses Kustomize for layering and substitution.
Templated configurationYYNNYY. Uses Kustomize
Centralized configuration modelYYYNYY
Ability to use existing machines (from machine provisioning stage)
YYYYTBD. Recognizes the use case of "bring your own OS", but not committed to implementing in v2.0.
Ability to manage underlying infrastructure (i.e. to create and configure nodes for use by a cluster)YNunknownNdepends on infra providerYes, integrates cluster-api-provider-metal3
Support for different architectures: Arm and x86YNNYunknownN.  ARM is out of scope for v2.0. Operators are welcome to step up and add the support.
K8s clusters pass conformance testYunknownYYunknownTBD, May run internally. 
100% open sourceYYYYYY
Support all CNCF-hosted projectsY


unknownYes. Airship is designed not in the way for users to deploy additional extensions and add-ons. If an extension has Helm charts, it can be optionally added to Airship life cycle management experience.







Support for specific versions of K8sYNYYYY
Specific versions of K8s componentsY


YY
etcdYunknownYYYY
Support for deploying from HEAD / `master` branch of K8sYNYYunknown?
Container runtimes (containerd, cri-o) with specific versionsYYNYYY, uses cluster api kubeadm provider
Kubernetes add-ons/extensions installation (e.g. CNI, CSI, Service Mesh, Ingress, LB, etc.)




Y







Hybrid Support both VNF and CNF




Y
Customizable - pick and choose what and when to use for installation




Y







...