-
Notifications
You must be signed in to change notification settings - Fork 612
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
feat: aws integration #967
Conversation
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome.
i have a question and a commnet.
what can we analyze only for eks? for cluster analyze, it is just same as normal k8sgpt since eks is cluster.
maybe we can use aws eks package itself not just k8s client.
and why not using k8sgpt global config kubeconfg
? and fix .kube/config
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i give 2 comments
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Closes #
π Description
β Checks
βΉ Additional Information
This initial integration will surface issues found in EKS beneath the current cluster