Skip to content
Snippets Groups Projects
Select Git revision
  • db693d46df77db5c23f17ecf45d6daf0f387e594
  • master default protected
  • v2.28.0
  • v2.27.0
  • v2.25.1
  • v2.24.3
  • v2.26.0
  • v2.24.2
  • v2.25.0
  • v2.24.1
  • v2.22.2
  • v2.23.3
  • v2.24.0
  • v2.23.2
  • v2.23.1
  • v2.23.0
  • v2.22.1
  • v2.22.0
  • v2.21.0
  • v2.20.0
  • v2.19.1
  • v2.18.2
22 results

cri-o.md

Blame
    • user avatar
    Fix etcd deployment type variable location (#5587)
    Fabiano Tessarolo authored and GitHub committed 
    On deployments types where etcd server is splitted from Kube Master, the deployment fails since it cannot find the variable.
    16fd2e5d
    History
    user avatar 16fd2e5d
    History
    cri-o.md 687 B

    CRI-O

    CRI-O is a lightweight container runtime for Kubernetes. Kubespray supports basic functionality for using CRI-O as the default container runtime in a cluster.

    • Kubernetes supports CRI-O on v1.11.1 or later.
    • Helm and other tools may not function as normal due to dependency on Docker.
    • scale.yml and upgrade-cluster.yml are not supported on clusters using CRI-O.

    To use CRI-O instead of Docker, set the following variables:

    all.yml

    download_container: false
skip_downloads: false

    k8s-cluster.yml

    kubelet_deployment_type: host
container_manager: crio

    etcd.yml

    etcd_deployment_type: host