Skip to content
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

Get endpoints as part of the diagnostics bundle #2603

Merged
merged 1 commit into from
Feb 25, 2020

Conversation

sebgl
Copy link
Contributor

@sebgl sebgl commented Feb 24, 2020

Some flaky E2E tests report no endpoints exist for the Elasticsearch
HTTP service. This may help to understand what is happening.

May help with #2602.

Some flaky E2E tests report no endpoints exist for the Elasticsearch
HTTP service. This may help to understand what is happening.
@sebgl sebgl added the >enhancement Enhancement of existing functionality label Feb 24, 2020
@@ -110,6 +110,7 @@ main() {
get_resources $ns persistentvolumes
get_resources $ns persistentvolumeclaims
get_resources $ns services
get_resources $ns endpoints
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if dumping this can become a problem on large installations.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean because of the high number of items?
It's probably the same cardinality as for Pods.

@sebgl sebgl merged commit 57e96b2 into elastic:master Feb 25, 2020
@pebrc pebrc added the v1.1.0 label Mar 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality v1.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants