You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
After updating the audit policy, restarting the rke2 server process, and performing requests on the cluster, I still do not any audit logs generated.
I'm not sure if this is expected behavior or not as I could not find upstream documentation about changing this.
Steps:
Create an rke2 server in cis mode
Update the data located in the audit policy file, located at: /etc/rancher/rke2/audit-policy.yaml, to log everything:
I think we already have an issue for this, at #692. The issue is that our selinux policy doesn't allow the apiserver pod to access the policy and log files.
Description:
After updating the audit policy, restarting the rke2 server process, and performing requests on the cluster, I still do not any audit logs generated.
I'm not sure if this is expected behavior or not as I could not find upstream documentation about changing this.
Steps:
/etc/rancher/rke2/audit-policy.yaml
, to log everything:sudo systemctl restart rke2-server
Notice there is no log file created:
sudo ls /var/lib/rancher/rke2/server/logs/
The text was updated successfully, but these errors were encountered: