Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add a switch to enable audit log dynamic backend #229

Closed
kdomanski opened this issue Mar 4, 2019 · 4 comments
Closed

Add a switch to enable audit log dynamic backend #229

kdomanski opened this issue Mar 4, 2019 · 4 comments
Assignees
@kron4eg
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
v0.4.0

Comments

@kdomanski
Copy link
Contributor

Reference: https://kubernetes.io/docs/tasks/debug-application-cluster/audit/#dynamic-backend

A config.yaml option features->audit_dynamic_configuration would be added, defaulting to false. Upon being set to true, it would result in the apiserver flags being added, that cause the dynamic audit config to be enabled.
@kron4eg kron4eg added this to the Someday milestone Mar 4, 2019
@kron4eg
Copy link
Member

kron4eg commented Mar 4, 2019

I'm not entirely sure should this issue replace #220 but this one is the purpose for what #220 what created.

@xmudrii
Copy link
Member

xmudrii commented Mar 5, 2019 •
edited
Loading

It is up to be decided how we want to configure such features: by providing some API fields and flags or by allowing user to push the whole configuration file (#220).

@kdomanski
Copy link
Contributor Author

Dynamic configuration is preferred.

@kron4eg
Copy link
Member

kron4eg commented Mar 5, 2019

oh, that makes things much easier (but vulnerable to attacker to tamper with settings)

@kron4eg kron4eg modified the milestones: Someday, v0.4.0 Mar 5, 2019
@xmudrii xmudrii added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Mar 5, 2019
@xmudrii xmudrii mentioned this issue Mar 5, 2019
Closed
@kron4eg kron4eg mentioned this issue Mar 13, 2019
Merged
@kron4eg kron4eg self-assigned this Mar 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kron4eg kron4eg

Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
3 participants
@kron4eg @kdomanski @xmudrii