openstack/devstack-plugin-container
Code Issues Proposed changes
Files
master
devstack-plugin-container/devstack/settings

36 lines
1.2 KiB
Plaintext
Raw Permalink Normal View History

Add docker installation script There are several projects that tried to install docker in different ways. This potentially lead to failure of more than one such services were enabled. This commit consolidate docker installation into a devstack plugin so that other services could depend on it. The initial script was mainly from Kuryr-libnetwork. Kuryr, Fuxi, and Zun might leverage this script to install Docker in the future. Change-Id: I97dbff2f361acc98b12ec6f40ab115c8548477a3
2017-04-13 00:56:04 -04:00
# Devstack settings
Add support for CRI-O as container engine This commit adds support for CRI-O. Support for Fedora/CentOS is in progress. Change-Id: Ib049d66058429e499f5d0932c4a749820bec73ff
2018-11-27 12:51:48 +01:00
# Supported options are "docker" and "crio".
Add docker installation script There are several projects that tried to install docker in different ways. This potentially lead to failure of more than one such services were enabled. This commit consolidate docker installation into a devstack plugin so that other services could depend on it. The initial script was mainly from Kuryr-libnetwork. Kuryr, Fuxi, and Zun might leverage this script to install Docker in the future. Change-Id: I97dbff2f361acc98b12ec6f40ab115c8548477a3
2017-04-13 00:56:04 -04:00
CONTAINER_ENGINE=${CONTAINER_ENGINE:-docker}
Add support for kata container Change-Id: I8de21dd0317734711ba3778c241a428f0325ea85
2019-07-01 15:22:08 +00:00
# TODO(hongbin): deprecate and remove clear container
Disable clear containers by default ENABLE_CLEAR_CONTAINER should be set to false by default as they're relying on third party repos which could break devstack installation at some point. Change-Id: I99b26650f6c68e8563dcde589bda7ccdc6a19a46
2018-01-25 12:43:37 +00:00
ENABLE_CLEAR_CONTAINER=${ENABLE_CLEAR_CONTAINER:-false}
Add support for kata container Change-Id: I8de21dd0317734711ba3778c241a428f0325ea85
2019-07-01 15:22:08 +00:00
ENABLE_KATA_CONTAINERS=${ENABLE_KATA_CONTAINERS:-false}
Support live_restore for keeping all running containers Change-Id: I5ca480bab5cb402dd7bd29f78dd8b6a639060fcf
2018-04-10 16:19:58 +08:00
ENABLE_LIVE_RESTORE=${ENABLE_LIVE_RESTORE:-false}
Configure the dokcer daemon for IPv6 Change-Id: If190af800a8c28e2cf4ae320a770c40847cd18e6
2019-01-29 09:40:31 +08:00
ENABLE_IPV6=${ENABLE_IPV6:-false}
Add Kubernetes job Change-Id: I2c75c81521ed8a53627119b231f526508154e34d
2019-06-15 22:10:48 +00:00
K8S_NETWORK_ADDON=${K8S_NETWORK_ADDON:-flannel}
Support enabling CRI for containerd Installing docker will install the CRI plugin for containerd. This commit support enabling the CRI-containerd plugin. By default, this is disabled. Change-Id: Ica8d5f91ae77d1d6599bfadc4031552016ad8953
2020-02-02 18:21:25 +00:00
ENABLE_CONTAINERD_CRI=${ENABLE_CONTAINERD_CRI:-false}
Change repository for k8s, cri-o The legacy k8s repository was retired on March 26, 2024 [1]. The cri-o project followed k8s lead and moved the build to a new repository [2]. This patch changes the location of k8s, cri-o installed packages for Ubuntu based deployments only. Changes the value of the apiversion parameter in the kubeadm configuration because the new repository can also install 1.27.x and later versions of k8s that no longer support v1beta2 and earlier APIs. The version of the package to be installed can be specified using the K8S_VERSION and CRIO_VERSION variables. Also, the default values of K8S_VERSION and CRIO_VERSION have been changed, and it has been confirmed that tacker project FT works fine with the changed version. [1]https://kubernetes.io/blog/2023/08/31/legacy-package-repository-deprecation/ [2]https://kubernetes.io/blog/2023/10/10/cri-o-community-package-infrastructure/ Change-Id: I0ce9fd2bcb5d79ebad2cecafabf8c9f33b106647
2024-08-21 07:43:21 +00:00
CRIO_VERSION=${CRIO_VERSION:-"1.30.5"}
Allow ICMP between pods for CRI-O. By default, CRI-O doesn't allow to have ICMP traffic between the pods and pods to/from host. It's convenient to have such ability for testing and debugging purpose. In this patch there is added appropriate configuration to crio.conf, and also a setting to disable it if needed. Change-Id: I1133815d9cbce311313bff7a219a9b3939390660
2021-11-09 11:55:56 +01:00
CRIO_ALLOW_ICMP=${CRIO_ALLOW_ICMP:-true}
Provide right path to the runc binary for Ubuntu and CRI-O installation. There are also two new configuration option introduced: - CNI_PLUGIN_DIR - CNI_CONF_DIR which, if defined, are used to configure crio paths for plugins and networks config. Change-Id: Ica4277b06740f8dca3ff5be77432cf6ab2f3cdeb
2021-10-27 13:58:53 +02:00
CNI_CONF_DIR=${CNI_CONF_DIR:-}
CNI_PLUGIN_DIR=${CNI_PLUGIN_DIR:-}
Add docker installation script There are several projects that tried to install docker in different ways. This potentially lead to failure of more than one such services were enabled. This commit consolidate docker installation into a devstack plugin so that other services could depend on it. The initial script was mainly from Kuryr-libnetwork. Kuryr, Fuxi, and Zun might leverage this script to install Docker in the future. Change-Id: I97dbff2f361acc98b12ec6f40ab115c8548477a3
2017-04-13 00:56:04 -04:00
Support installing specific version of docker Change-Id: I12015c28f6f8ffc125097a14514a6a90a20cf35b
2023-02-24 15:11:02 +00:00
UBUNTU_DOCKER_VERSION=${UBUNTU_DOCKER_VERSION:-}
Add docker installation script There are several projects that tried to install docker in different ways. This potentially lead to failure of more than one such services were enabled. This commit consolidate docker installation into a devstack plugin so that other services could depend on it. The initial script was mainly from Kuryr-libnetwork. Kuryr, Fuxi, and Zun might leverage this script to install Docker in the future. Change-Id: I97dbff2f361acc98b12ec6f40ab115c8548477a3
2017-04-13 00:56:04 -04:00
# Enable container services
enable_service container
Support k8s installation Add support for installing kubernetes cluster via devstack. It uses kubeadm to bootstrap the k8s cluster. Change-Id: I7877ceda08bbdab807116a13d74ff884136dc501
2019-03-23 20:55:16 +00:00
# Enable k8s services
if [[ ,${ENABLED_SERVICES} =~ ,"k8s-master" ]]; then
enable_service kube-controller-manager
enable_service kube-apiserver
enable_service kube-scheduler
enable_service kube-proxy
fi
Support config image repository for kubeadm In some places of which network environment was limited, kubeadm can't pull images from k8s.gcr.io. This patch add a variable `KUBEADMIN_IMAGE_REPOSITORY` in order to the developer who located in these places can set the kubeadm to pull container images from repository that they can access. Change-Id: I14aed50077ef0760635e575770fd2274cb759c53
2022-03-20 11:29:47 +08:00
# Customize kubeadm container images repository
Change default kubernetes registry to current one. Last year, kubernetes community has made a move from k8s.gcr.io to registry.k8s.io. Currently images on k8s.gcr.io has been stopped from serving therefore, there is a need to migrate to the new one. Change-Id: I20305b380d26fdaa30632107b29debc519e13e54
2023-02-21 16:47:52 +01:00
KUBEADMIN_IMAGE_REPOSITORY=${KUBEADMIN_IMAGE_REPOSITORY:-"registry.k8s.io"}
Support config pause image for crio In some places of which network environment was limited, ciro can't pull images from k8s.gcr.io. This patch add a variable `CRIO_PAUSE_IMAGE` in order to the developer who located in these places can set the ciro to pull pause container images from repository that they can access. The `CRIO_PAUSE_COMMAND` used to configure crio's `pause_command` (the pause container's bootstrap command), in order to the developer can use the special pause image the they customized. Change-Id: Ib0d4c42870d40ef583546758513a36b906c7663b
2022-03-20 11:47:25 +08:00
# Configure crio pause image
Change default kubernetes registry to current one. Last year, kubernetes community has made a move from k8s.gcr.io to registry.k8s.io. Currently images on k8s.gcr.io has been stopped from serving therefore, there is a need to migrate to the new one. Change-Id: I20305b380d26fdaa30632107b29debc519e13e54
2023-02-21 16:47:52 +01:00
CRIO_PAUSE_IMAGE=${CRIO_PAUSE_IMAGE:-"registry.k8s.io/pause:3.6"}
Support config pause image for crio In some places of which network environment was limited, ciro can't pull images from k8s.gcr.io. This patch add a variable `CRIO_PAUSE_IMAGE` in order to the developer who located in these places can set the ciro to pull pause container images from repository that they can access. The `CRIO_PAUSE_COMMAND` used to configure crio's `pause_command` (the pause container's bootstrap command), in order to the developer can use the special pause image the they customized. Change-Id: Ib0d4c42870d40ef583546758513a36b906c7663b
2022-03-20 11:47:25 +08:00
CRIO_PAUSE_COMMAND=${CRIO_PAUSE_COMMAND:-"/pause"}
Copy Permalink