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

Add documenation for AWS pod identity providers #56

Merged
merged 7 commits into from
Feb 5, 2020

Conversation

zach-dunton-sf
Copy link
Contributor

No description provided.

Copy link
Member

@tomkerkhove tomkerkhove left a comment

Choose a reason for hiding this comment

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

LGTM - Added a few small suggestions but overall very clear, thank you!

@jeffhollan @ahmelsayed We might want to introduce some version information in our docs so that folks know when it is introduced. Thoughts?

content/scalers/aws-cloudwatch.md Outdated Show resolved Hide resolved
content/scalers/aws-sqs.md Outdated Show resolved Hide resolved
content/scalers/aws-sqs.md Outdated Show resolved Hide resolved
content/scalers/aws-cloudwatch.md Outdated Show resolved Hide resolved
content/concepts/authentication/content.md Outdated Show resolved Hide resolved
content/concepts/authentication/content.md Outdated Show resolved Hide resolved
provider: kiam # Optional. Default: false
```

Kiam will give access to containers based on the role provided by the `iam.amazonaws.com/role` annotation on the pod.
Copy link
Member

Choose a reason for hiding this comment

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

Thinking out loud - Since this is documentation on how to configure it for our dependency, should we document this here or merely point to their docs? For example, what if they change their approach?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I do not expect kiam to change. I assume it will be superseded, rather than changed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can remove these lines though. I understand the skepticism of essentially documenting another project.

Copy link
Member

Choose a reason for hiding this comment

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

Maybe just add a link instead, but I think you already did it somewhere else, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's in the first paragraph. I will remove thsese sections.

zach-dunton-sf and others added 5 commits December 9, 2019 10:49
Co-Authored-By: Tom Kerkhove <kerkhove.tom@gmail.com>
Co-Authored-By: Tom Kerkhove <kerkhove.tom@gmail.com>
'kiam' -> 'aws-kiam'
'eks'  -> 'aws-eks'
Copy link
Member

@jeffhollan jeffhollan left a comment

Choose a reason for hiding this comment

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

Apologies know this has been open for a bit. This LGTM. @zach-dunton-sf is this still accurate and ready to merge in?

@tomkerkhove
Copy link
Member

LGTM, ok to merge or still pending changes @zach-dunton-sf ?

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.

3 participants