Skip to content

Add information for collecting Kubernetes information using script provided in the aws-samples organization on GitHub.#1195

Open
yuidexebiuy wants to merge 1 commit into
awsdocs:mainlinefrom
yuidexebiuy:patch-2
Open

Add information for collecting Kubernetes information using script provided in the aws-samples organization on GitHub.#1195
yuidexebiuy wants to merge 1 commit into
awsdocs:mainlinefrom
yuidexebiuy:patch-2

Conversation

@yuidexebiuy

Copy link
Copy Markdown

Issue #, if available:

Description of changes:
Add information for collecting Kubernetes information using script provided in the aws-samples organization on GitHub.
Previous Pull Request #1165 was closed, so resubmitting.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

…ovided in the aws-samples organization on GitHub.
@yuidexebiuy yuidexebiuy requested a review from a team as a code owner December 23, 2025 04:08
@aws-amplify-us-east-1

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1195.d3rijirjvbh87e.amplifyapp.com

[#k8s-log-collector]
=== EKS Kubernetes Log Collector

To troubleshoot Kubernetes issues on Amazon EKS, You can use the script to collect diagnostic logs for support cases and general troubleshooting.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

nit. typo "you can use..." (no capital word in the middle of the sentence)

$ bash eks-pod-information-collector.sh -p pod_name -n pod_namespace -s service_name
Script execution started...
Validating input arguments...
Collected Cluster Name: "{Cluster_name}}" from current context...

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

typo? unmatched brace {Cluster_name}}, but this might be from the script output itself?

Archiving collected information...

Done!! Archived information is located in "./<Cluster_Name_Start_Timestamp>.tar.gz"
Check the execution logs in file ./<Cluster_Name_Start_Timestamp>/EPIC-Script_<Start_Timestamp>>.log!!"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

same here with <Start_Timestamp>>


To troubleshoot Kubernetes issues on Amazon EKS, You can use the script to collect diagnostic logs for support cases and general troubleshooting.

==== To collect general overall information about Kubernetes, use https://github.com/aws-samples/sample-eks-k8s-information-collector[EKS Kubernetes Information Collector].

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

nit: This heading and others in the file are phrased as sentences rather than noun-phrase titles, not matching the style of the rest of the doc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants