Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Heapster-dashboard integration broken out of the box
See original GitHub issueOn a fresh EKS cluster with deployDashboard: true (as available in this repo’s heapster-broken branch) the “CPU usage” and “Memory usage” graphs are not visible.
I suspect the problem is related to https://github.com/awslabs/amazon-eks-ami/issues/128.
For what it’s worth, by following the advice in one of the comments to the linked issue, I was able to get heapster working again in https://github.com/MerelyAPseudonym/eks-pulumi-repro/commit/6effd13cef11a55ae6afd1a29fdaffeab01b4cdd. (Security concerns might prevent that from being acceptable default behavior, though.)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m in favor of deprecating the dashboard for the aforementioned reasons
I’m closing this issue to track the separate tasks here:
Please let us know if you have any other questions or comments. Thanks!