-
Notifications
You must be signed in to change notification settings - Fork 201
Added AWS Credentials Support for Scanning Private Registry (ECR) #1103
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
base: main
Are you sure you want to change the base?
Changes from 4 commits
b875dc8
1411d12
d361d7f
23bce93
58fb2c0
bc24ddd
10768d2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,12 +6,12 @@ type: application | |
| # This is the chart version. This version number should be incremented each time you make changes | ||
| # to the chart and its templates, including the app version. | ||
| # Versions are expected to follow Semantic Versioning (https://semver.org/) | ||
| version: 0.10.0 | ||
| version: 0.10.2 | ||
|
danielpacak marked this conversation as resolved.
Outdated
|
||
|
|
||
| # This is the version number of the application being deployed. This version number should be | ||
| # incremented each time you make changes to the application. Versions are not expected to | ||
| # follow Semantic Versioning. They should reflect the version the application is using. | ||
| appVersion: 0.15.0 | ||
| appVersion: 0.15.1 | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this file should be restored as it was , we only change versions when we release
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Changed back to normal. |
||
| # kubeVersion: A SemVer range of compatible Kubernetes versions (optional) | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -118,6 +118,18 @@ trivy: | |
| # | ||
| # noProxy: | ||
|
|
||
| # Allows to fetch the ECR Login Token if the Service is running in AWS and the EC2-VM has an Instance-Role assigned. | ||
| # It also needs k8s KIAM (https://github.com/uswitch/kiam) to be in place which allowed Assuming Roles to specify | ||
| # dedicated permissions for the Finale Role which has the rights to get login credentials. | ||
| # | ||
| # useEcrRoleCreds: false | ||
|
|
||
| # Set the TokenExpiry for the next AWS-Tokengeneration | ||
| # AWS authorization token is valid for 12 hours by default | ||
| # Unit is hours(h) | ||
| # | ||
| # ecrTokenRefreshTTL = 11h | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, maybe a retry logic should be placed for
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, Trivy will never use an expired token as in the original part I pushed, the Token creation was part of "each" individual request Trivy did per repository. The only reason we have this timer now in place is to reduce the number of requests (Throttling) against the ECR-API. So, if you want to detect an expired token and you want to make it part of a retry to refresh the token now you need to get the first trivy job triggered which tries to get the image and will run into the error. As of now, I see no point in that we need that. The Throttling does its job, and it is up to the implementer to configure the TTLs on their own. In my view, this is the best approach. |
||
|
|
||
| # Registries without SSL. There can be multiple registries with different keys. | ||
| nonSslRegistries: {} | ||
| # pocRegistry: poc.myregistry.harbor.com.pl | ||
|
|
@@ -435,6 +447,11 @@ serviceAccount: | |
| # podAnnotations annotations added to the operator's pod | ||
| podAnnotations: {} | ||
|
|
||
| # podAnnotations example for to get the ECR-Credentials fetch working via AWS-Roles | ||
| # | ||
| # podAnnotations: | ||
| # iam.amazonaws.com/role: <yourRolewithPermissions> | ||
|
|
||
| podSecurityContext: {} | ||
| # fsGroup: 2000 | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.