deckhouse / deckhouse/deckhouse
[control-plane-manager] unobvious audit logs management
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 162
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 653
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Version
v1.44
Expected Behavior
It should be obvious that basicAuditPolicyEnabled configuration is designed to audit deckhouse components.
There should be similar flag to configure standard audit policies for applications. Or handy examples.
Actual Behavior
There is basicAuditPolicyEnabled flag. After enabling it i'm counting that there will be audit logs for creating random ClusterRoles for example. But there aren't.
Steps To Reproduce
No response
Additional Information
No response
Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the control-plane-manager configuration for basicAuditPolicyEnabled and review how it relates to Kubernetes audit logs and ClusterRoles. Compare the documented behavior with the expected application-audit behavior described here. Done should be a clearly defined application audit configuration or handy examples that make the scope of the existing flag unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- observability, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100