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

disable-access-log at the ingress level #2087

Closed
Stono opened this issue Feb 14, 2018 · 1 comment · Fixed by #2144
Closed

disable-access-log at the ingress level #2087

Stono opened this issue Feb 14, 2018 · 1 comment · Fixed by #2144
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Stono
Copy link
Contributor

Stono commented Feb 14, 2018

Hey,
It'd be great if there was an ingress level control for the access-log, rather than the current overall configmap.

As an example; we have an ELK stack where the logs from elasticsearch ingress (from logstash) create a LOT of logs, and we don't want these, however we are very interested in user logs hitting Kibana.

They're defined as separate ingresses so being able to annotate the elasticsearch one with disable-access-log: true would be a big win for us.

@aledbf aledbf added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. labels Feb 14, 2018
@aledbf
Copy link
Member

aledbf commented Feb 14, 2018

@Stono sure, in the meantime you can use the snippet annotation to disable the logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants