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.

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

Auditing topic is unclear, missing information #6365

Closed
1 of 2 tasks
Bradamant3 opened this issue Nov 17, 2017 · 5 comments
Closed
1 of 2 tasks

Auditing topic is unclear, missing information #6365

Bradamant3 opened this issue Nov 17, 2017 · 5 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@Bradamant3
Copy link
Contributor

This is a...

  • Feature Request
  • Bug Report

Problem:
The Auditing topic is unclear and is missing important information.

Proposed Solution:
Rewrite the topic for clearer structure and complete information. Specifically note the following (and check with tech reviewers to add anything else):

  • Audit logging must be explicitly enabled
  • There is no default location for the logs (IOW, specifying a log location is required when you enable -- it's not as simple as setting a single flag/option/argument)

Page to Update:
https://kubernetes.io/docs/tasks/debug-application-cluster/audit/

Additional Information:
Make sure to keep information about differences in behavior in different versions. Consider checking for planned changes in upcoming releases.

@tengqm
Copy link
Contributor

tengqm commented Nov 29, 2017

#6427

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 27, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 29, 2018
@shubheksha
Copy link
Contributor

@Bradamant3, @tengqm - has this been fixed in PR #6427? Can this be closed?

@tengqm
Copy link
Contributor

tengqm commented Apr 23, 2018

@shubheksha Thanks for remindering. Let's close it for now. It looks to me #6427 has solved this issue.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants