Sink Architecture in PKS
Page last updated:
Warning: Pivotal Container Service (PKS)
v1.3 is no longer supported because it has reached the End
of General Support (EOGS) phase as defined by the
Support Lifecycle Policy.
To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic describes how sinks are implemented in Pivotal Container Service (PKS) workloads.
The following diagram details sink architecture in PKS.
Logs are monitored by a set of fluent-bit daemons, which run as a pod on each node.
When sinks are added or removed, all the fluent-bit pods are refreshed with new sink information.
Another pod collects Kubernetes API events and sends them to a fluent-bit pod.
For more information on sinks in PKS, see the following topics:
- For information about creating sinks in PKS, see Creating Sink Resources.
- For information about using sinks for monitoring, see Monitoring PKS with Sinks.
Please send any feedback you have to email@example.com.