Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1692072

Summary: [RFE]: mmkubernetes: support cache expiration
Product: Red Hat Enterprise Linux 8 Reporter: Rich Megginson <rmeggins>
Component: rsyslogAssignee: Jiří Vymazal <jvymazal>
Status: CLOSED ERRATA QA Contact: Dalibor Pospíšil <dapospis>
Severity: medium Docs Contact: Mirek Jahoda <mjahoda>
Priority: medium    
Version: 8.0CC: dapospis, jvymazal, rmeggins
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 8.2Flags: pm-rhel: mirror+
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 
Description of problem:
mmkubernetes has a static cache - if Kubernetes objects are deleted, the cache should be cleared.  It is good enough to support a cache entry ttl as in fluent-plugin-kubernetes_metadata_filter



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
https://github.com/rsyslog/rsyslog/pull/3539
Comment 1 Rich Megginson 2019-03-24 01:59:24 UTC 
docs: https://github.com/rsyslog/rsyslog-doc/pull/792
Comment 2 Rich Megginson 2019-04-03 13:29:05 UTC 
merged upstream: https://github.com/rsyslog/rsyslog/commit/f4ed61e9cedcf09634c3ef35a5550e1c3cf2c9e4
docs: https://github.com/rsyslog/rsyslog-doc/commit/1ce29da1267585b66231503e59ae91d290649e19
Comment 9 errata-xmlrpc 2020-04-28 16:01:03 UTC 
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