-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auditd on talos 1.9 #9907
Comments
Talos Do you have a reproducer showing that auditd when deployed as a pod (or whatever way you deploy it) no longer works? If you do, we can look into that. |
From linux-audit/audit-kernel#102 it seems its possible to run as a listener without |
Please show us a way to reproduce the problem, and we can look for a solution, a solution without a problem doesn't quite work. |
On talos v1.9.1 I get the following error when running my auditd workload:
Stripped down manifests to reproduce this: ---
# Source: auditd/templates/namespace.yaml
apiVersion: v1
kind: Namespace
metadata:
name: audit
labels:
pod-security.kubernetes.io/enforce: privileged
app.kubernetes.io/part-of: auditd
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: auditd
namespace: audit
labels:
app.kubernetes.io/name: auditd
app.kubernetes.io/instance: auditd
app.kubernetes.io/version: "4.0.1"
app.kubernetes.io/part-of: auditd
spec:
selector:
matchLabels:
app.kubernetes.io/name: auditd
app.kubernetes.io/instance: auditd
template:
metadata:
labels:
app.kubernetes.io/name: auditd
app.kubernetes.io/instance: auditd
app.kubernetes.io/part-of: auditd
app.kubernetes.io/version: "4.0.1"
spec:
hostPID: true
containers:
- name: auditd
image: "stereobutter/auditd:latest"
imagePullPolicy: "IfNotPresent"
securityContext:
runAsUser: 0
capabilities:
add:
- AUDIT_CONTROL
- AUDIT_WRITE
- SYS_RESOURCE
- SYS_NICE
volumeMounts:
- name: run
mountPath: /var/run
- name: rules
mountPath: /etc/audit/rules.d
volumes:
- name: run
hostPath:
path: /var/run
type: DirectoryOrCreate
- name: rules
emptyDir: {}
|
Fixes siderolabs#9907 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com> (cherry picked from commit db4ca56)
Feature Request
Provide a way to run user-provided
auditd
on talos v1.9.Description
As per #9620 talos v1.9 comes with an auditd-like service. @frezbo told me the motivation for this feature is debugging SELinux policies. As the feature is implemented right now I believe this can not run in tandem with a user-provided
auditd
since IIRC only one application may bind to the kernel's audit socket.Possible solutions:
auditd
serviceauditd
since it isn't a real instance (or 1:1 implementation) ofauditd
.The text was updated successfully, but these errors were encountered: