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

Update addon-id-troubleshoot.adoc for EKS Pod Identity. #894

Open
wants to merge 1 commit into
base: mainline
Choose a base branch
from

Conversation

entropyReverser
Copy link

Description of changes:
Adds additional debug step for EKS pod identity implementation.

Hey found this out after spending time debugging with 3 different AWS Support engineers. Everything was setup using the AWS Docs from here https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html . The same config was working on the support engineer's cluster but failing on our cluster. Then we ran this query on the Cloudwatch Log insights on the eks cluster logs

fields @timestamp, @message
| filter @logStream like /kube-apiserver/ and @logStream not like /kube-apiserver-audit/
| filter @message like /failed calling webhook/
| sort @timestamp desc

Which showed us some errors in the mutating webhooks then we compared the YAML of ours and their cluster's pod-identity-webhook MutatingWebhookConfiguration which led us to this discovery. Their webhook was on v1Beta1 while ours was on V1.

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

Adds additional debug step for EKS pod identity implementation.

Hey found this out after spending time debugging with 3 different AWS Support engineers. Everything was setup using the  AWS Docs from here https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html
The same config was working on the support engineer's cluster but failing on our cluster. 
Then we ran this query on the Cloudwatch Log insights on the eks cluster logs

```
fields @timestamp, @message
| filter @logstream like /kube-apiserver/ and @logstream not like /kube-apiserver-audit/
| filter @message like /failed calling webhook/
| sort @timestamp desc
```
Which showed us some errors in the mutating webhooks then we compared the YAML of ours and their pod-identity-webhook MutatingWebhookConfiguration which led us to this discovery. Their webhook was on v1Beta1 while ours was on V1.
Copy link

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

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

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.

1 participant