rsyslog/tests/mmkubernetes.supp
Rich Megginson 3987cd929d mmkubertnetes: action fails preparation cycle if kubernetes API destroys resource during bootup sequence
The plugin was not handling 404 Not Found correctly when looking
up pods and namespaces.  In this case, we assume the pod/namespace
was deleted, annotate the record with whatever metadata we have,
and cache the fact that the pod/namespace is missing so we don't
attempt to look it up again.
In addition, the plugin was not handling error 429 Busy correctly.
In this case, it should also annotate the record with whatever
metadata it has, and _not_ cache anything.  By default the plugin
will retry every 5 seconds to connect to Kubernetes.  This
behavior is controlled by the new config param `busyretryinterval`.
This commit also adds impstats counters so that admins can
view the state of the plugin to see if the lookups are working
or are returning errors.  The stats are reported per-instance
or per-action to facilitate using multiple different actions
for different Kubernetes servers.
This commit also adds support for client cert auth to
Kubernetes via the two new config params `tls.mycert` and
`tls.myprivkey`.
2018-09-14 12:42:06 -06:00

17 lines
316 B
Plaintext

{
mmkubernetes: says hashtables are leaked at shutdown but they are freed - not sure what is the problem here
Memcheck:Leak
fun:malloc
fun:create_hashtable
obj:*
obj:*
fun:doModInit
fun:Load
fun:UseObj
fun:modInit
fun:doModInit
fun:Load
fun:modulesProcessCnf
fun:cnfDoObj
}