Please detail control plane logging architecture.

[timmycarr]

Please clarify the control plane log sink architecture. Workload nodes are called out as running a daemonset to collect needed logs, but we don't run kubelet on control plane components in PKS, therefore a daemonset won't schedule log collection resources there. Please clairfy in the architecture doc, what services are running on what cluster component and how they are controlled with regards to log collection.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[pspinrad]

Thanks for the suggestion @timmycarr -- good timing, because we were already planning to revise those docs and diagrams soon.

what services are running on what cluster component and how they are controlled with regards to log collection

[pspinrad]

Hi @timmycarr @eshanks16 -- do these revised topics clarify the logging architecture?

• https://docs.pivotal.io/tkgi/1-8/sink-architecture.html#sink-architecture
• https://docs.pivotal.io/tkgi/1-8/monitor-audit-logs.html