You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep historical data for a period of time and check it at any time (such as: when the log uses hostpath mode, you can quickly locate the node where the pod is located and the log file)
The text was updated successfully, but these errors were encountered:
Hi @bertreyking,
Thanks for opening an issue!
We will look into it as soon as possible.
Details
Instructions for interacting with me using comments are available here.
If you have questions or suggestions related to my behavior, please file an issue against the gh-ci-bot repository.
Sorry(Problem 2 does not seem to need to be resolved),today I found that the resource information has been differentiated by different resource and kind in the (db)resources table
mysql:
SELECT * FROM clusterpedia.resources where resource = 'deployments' limit 2 \G
SELECT * FROM clusterpedia.resources where resource = 'pods' limit 1 \G
What would you like to be added?
Use cronjob to complete resource information collection and email sending (to cc)
Resources are distinguished by tables such as: pod, deployment
Why is this needed?
Keep historical data for a period of time and check it at any time (such as: when the log uses hostpath mode, you can quickly locate the node where the pod is located and the log file)
The text was updated successfully, but these errors were encountered: