-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please detail control plane logging architecture. #1134
Comments
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. |
Thanks for the suggestion @timmycarr -- good timing, because we were already planning to revise those docs and diagrams soon.
|
Hi @timmycarr @eshanks16 -- do these revised topics clarify the logging architecture? |
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.
The text was updated successfully, but these errors were encountered: