
* It looks like zuul-jobs-test-registry-buildset-registry-k8s-crio is busted with Ubuntu Jammy + cri-o installed from kubic, with errors like https://github.com/cri-o/ocicni/issues/77 (also, kubic has been wound down and cri-o has been spun off) * cri-o in Noble uninstalls docker-ce, in a follow-up we should clean that up and switch to a pure podman profile * This minikube configuration is not supported, but it seems that upstream cri-o might have made some fixes that makes it work * Update the job to use Ubuntu Noble instead of Jammy * Update ensure-podman for Ubuntu Noble (podman is now part of the Ubuntu distro) * Update the cri-o install in ensure-minikube for Ubuntu Noble and later (cri-o is now part of k8s) Other miscellaneous fixes and workarounds: * k8s.gcr.io is being sunsetted, updated the test image: https://kubernetes.io/blog/2023/03/10/image-registry-redirect/ * Relaxed the security to run minikube from /tmp (in future, we should set the default to /usr/local/bin) * Updated the microk8s check-distro task for Noble Change-Id: I3b0cbac5c72c31577797ba294de8b8c025f8c2c3
63 lines
1.7 KiB
YAML
63 lines
1.7 KiB
YAML
- name: Add all repositories
|
|
# Instructions from here: https://github.com/cri-o/packaging making
|
|
# the assumption that CRIO_VERSION == KUBERNETES_VERSION
|
|
include_role:
|
|
name: ensure-package-repositories
|
|
vars:
|
|
repositories_keys:
|
|
- url: "https://pkgs.k8s.io/core:/stable:/{{ ensure_kubernetes_kubectl_version }}/deb/Release.key"
|
|
- url: "https://pkgs.k8s.io/addons:/cri-o:/stable:/{{ ensure_kubernetes_kubectl_version }}/deb/Release.key"
|
|
repositories_list:
|
|
- repo: "deb https://pkgs.k8s.io/core:/stable:/{{ ensure_kubernetes_kubectl_version }}/deb/ /"
|
|
- repo: "deb https://pkgs.k8s.io/addons:/cri-o:/stable:/{{ ensure_kubernetes_kubectl_version }}/deb/ /"
|
|
|
|
- name: Install packages
|
|
package:
|
|
name:
|
|
- cri-o
|
|
- runc
|
|
- containernetworking-plugins
|
|
- cri-tools
|
|
- podman
|
|
- kubernetes-cni
|
|
state: present
|
|
become: true
|
|
|
|
# The the following two options are recommended from cri-o install notes
|
|
- name: Enable ipv4 forwarding
|
|
sysctl:
|
|
name: net.ipv4.ip_forward
|
|
value: '1'
|
|
sysctl_set: true
|
|
state: present
|
|
reload: true
|
|
become: true
|
|
|
|
- name: Load br_netfilter
|
|
modprobe:
|
|
name: br_netfilter
|
|
state: present
|
|
persistent: present
|
|
become: true
|
|
|
|
- name: Find networking plugins
|
|
ini_file:
|
|
path: /etc/crio/crio.conf
|
|
section: crio.network
|
|
option: plugin_dirs
|
|
value:
|
|
- '/opt/cni/bin/'
|
|
- '/usr/lib/cni'
|
|
mode: 0644
|
|
become: true
|
|
register: _crio_conf_updated
|
|
|
|
# NOTE: want to restart here rather than notify and do it later, so
|
|
# that we don't go on without the config correct.
|
|
- name: Restart crio to pickup changes # noqa no-handler
|
|
service:
|
|
name: crio
|
|
state: restarted
|
|
become: yes
|
|
when: _crio_conf_updated.changed
|