Bug 1692072
Summary: | [RFE]: mmkubernetes: support cache expiration | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Rich Megginson <rmeggins> |
Component: | rsyslog | Assignee: | Jiří Vymazal <jvymazal> |
Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> |
Severity: | medium | Docs Contact: | Mirek Jahoda <mjahoda> |
Priority: | medium | ||
Version: | 8.0 | CC: | dapospis, jvymazal, rmeggins |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
Target Release: | 8.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | rsyslog-8.1911.0-1.el8 | Doc Type: | Enhancement |
Doc Text: |
.`rsyslog` `mmkubernetes` now provides metadata cache expiration
With this update of the `rsyslog` packages, you can use two new parameters for the `mmkubernetes` module for setting metadata cache expiration. This ensures that deleted Kubernetes objects are removed from the `mmkubernetes` static cache. The value of the `cacheentryttl` parameter indicates the maximum age of cache entries in seconds. The `cacheexpireinterval` parameter has the following values:
* `-1` for disabling cache-expiration checks
* `0` for enabling cache-expiration checks
* greater than 0 for regular cache-expiration checks in seconds
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:01:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1740683 | ||
Bug Blocks: |
Description
Rich Megginson
2019-03-24 01:47:28 UTC
merged upstream: https://github.com/rsyslog/rsyslog/commit/f4ed61e9cedcf09634c3ef35a5550e1c3cf2c9e4 docs: https://github.com/rsyslog/rsyslog-doc/commit/1ce29da1267585b66231503e59ae91d290649e19 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1702 |