mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-10-20 11:28:42 +00:00
9acf4e5d32
This is **not** the nicest patch of my career, and I know it adds code duplication. However, I've decided to take this approach in order to have easier / better instructions for users who're consuming kata-deploy. Having both stable & latest yaml on `main` will let us point to just one place, without having to update the instructions. I know, would be better to have those generated from a .in file, wouldn't it? For sure, but then we'd lose the ability to just point to those files from kata-deploy pages (either on dockerhub or quay.io). Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
47 lines
1.1 KiB
YAML
47 lines
1.1 KiB
YAML
---
|
|
apiVersion: apps/v1
|
|
kind: DaemonSet
|
|
metadata:
|
|
name: kubelet-kata-cleanup
|
|
namespace: kube-system
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
name: kubelet-kata-cleanup
|
|
template:
|
|
metadata:
|
|
labels:
|
|
name: kubelet-kata-cleanup
|
|
spec:
|
|
serviceAccountName: kata-label-node
|
|
nodeSelector:
|
|
katacontainers.io/kata-runtime: cleanup
|
|
containers:
|
|
- name: kube-kata-cleanup
|
|
image: quay.io/kata-containers/kata-deploy:stable
|
|
imagePullPolicy: Always
|
|
command: [ "bash", "-c", "/opt/kata-artifacts/scripts/kata-deploy.sh reset" ]
|
|
env:
|
|
- name: NODE_NAME
|
|
valueFrom:
|
|
fieldRef:
|
|
fieldPath: spec.nodeName
|
|
securityContext:
|
|
privileged: false
|
|
volumeMounts:
|
|
- name: dbus
|
|
mountPath: /var/run/dbus
|
|
- name: systemd
|
|
mountPath: /run/systemd
|
|
volumes:
|
|
- name: dbus
|
|
hostPath:
|
|
path: /var/run/dbus
|
|
- name: systemd
|
|
hostPath:
|
|
path: /run/systemd
|
|
updateStrategy:
|
|
rollingUpdate:
|
|
maxUnavailable: 1
|
|
type: RollingUpdate
|