Skip to content

Conversation

@qswinson
Copy link
Contributor

@qswinson qswinson commented Sep 17, 2025

Fixes #8437

Proposed Changes

This PR adds support for using the pod AWS default credentials for IntegrationSource and IntegrationSink resources. It adds an optional property .spec.aws.auth.serviceAccountName to specify the ServiceAccount the pod should run as. The ServiceAccount applies the desired role to the pod as the default credentials.

This change requires the latest images from aws-*-source in order for the Camel useDefaultCredentialsProvider property to be loaded from the environment variable.

Pre-review Checklist

  • At least 80% unit test coverage
  • E2E tests for any new behavior
  • Docs PR for any user-facing impact
  • Spec PR for any new API feature
  • Conformance test for any change to the spec

Release Note

Add support for using Pod default credentials in AWS IntegrationSource and IntegrationSink resources by specifying a ServiceAccount.

Docs
knative/docs#6394

@knative-prow
Copy link

knative-prow bot commented Sep 17, 2025

Welcome @qswinson! It looks like this is your first PR to knative/eventing 🎉

@knative-prow knative-prow bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 17, 2025
@knative-prow
Copy link

knative-prow bot commented Sep 17, 2025

Hi @qswinson. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@dprotaso
Copy link
Member

/ok-to-test

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 18, 2025
@codecov
Copy link

codecov bot commented Sep 18, 2025

Codecov Report

❌ Patch coverage is 43.18182% with 25 lines in your changes missing coverage. Please review.
✅ Project coverage is 50.60%. Comparing base (bfd6957) to head (f282427).
⚠️ Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
...iler/integration/sink/resources/container_image.go 42.85% 11 Missing and 1 partial ⚠️
...er/integration/source/resources/containersource.go 47.61% 10 Missing and 1 partial ⚠️
pkg/apis/common/integration/v1alpha1/auth.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8731      +/-   ##
==========================================
+ Coverage   50.23%   50.60%   +0.36%     
==========================================
  Files         409      409              
  Lines       26665    26707      +42     
==========================================
+ Hits        13396    13515     +119     
+ Misses      12427    12341      -86     
- Partials      842      851       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dprotaso
Copy link
Member

/retest

Copy link
Member

@dprotaso dprotaso 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 question for the maintainers.

AccessKey string `json:"accessKey,omitempty"`

// SecretKey is the AWS secret access key.
SecretKey string `json:"secretKey,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

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

@matzew @creydr how come I don't see this and accessKey field in the Integration* CRDs. Is stuff read from the secret and then these fields populated?

Copy link
Member

Choose a reason for hiding this comment

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

yes, that is via secret and there populated

@qswinson
Copy link
Contributor Author

/retest

@dprotaso
Copy link
Member

@qswinson I don't think it's a flake but a side-effect of something in your PR.

Looking at the testgrid here the test is stable - https://testgrid.k8s.io/r/knative-own-testgrid/eventing#continuous&include-filter-by-regex=TestIntegrationSourceWithTLS

@dprotaso
Copy link
Member

cc @matzew @creydr for a review in the meantime

}...)
} else {
envVars = append(envVars, corev1.EnvVar{
Name: "CAMEL_KAMELET_AWS_S3_SOURCE_USEDEFAULTCREDENTIALSPROVIDER",
Copy link
Member

Choose a reason for hiding this comment

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

I think we should use the new version of supported ENV_VARs, seE: https://github.com/knative-extensions/eventing-integrations/blob/main/aws-s3-sink/properties.adoc

/cc @christophd

Choose a reason for hiding this comment

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

yes +1 for more readability

@knative-prow
Copy link

knative-prow bot commented Oct 1, 2025

@matzew: GitHub didn't allow me to request PR reviews from the following users: christophd.

Note that only knative members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

I think we should use the new version of supported ENV_VARs, seE: https://github.com/knative-extensions/eventing-integrations/blob/main/aws-s3-sink/properties.adoc

/cc @christophd

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@dprotaso
Copy link
Member

dprotaso commented Oct 2, 2025

/test reconciler-tests_eventing_main

@dprotaso
Copy link
Member

dprotaso commented Oct 2, 2025

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2025
@dprotaso
Copy link
Member

dprotaso commented Oct 2, 2025

Leaving approval for @matzew & @creydr

Copy link
Member

@matzew matzew left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@knative-prow
Copy link

knative-prow bot commented Oct 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew, qswinson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 8, 2025
@dprotaso
Copy link
Member

dprotaso commented Oct 8, 2025

/retest

@knative-prow knative-prow bot added area/test-and-release Test infrastructure, tests or release and removed lgtm Indicates that a PR is ready to be merged. labels Oct 8, 2025
@dprotaso
Copy link
Member

dprotaso commented Oct 8, 2025

I pushed a change increase the timeout. The reconciler failures were from cert manager certs not being deleted fast enough.

@creydr
Copy link
Member

creydr commented Oct 8, 2025

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Oct 8, 2025
@knative-prow knative-prow bot merged commit 3f59df1 into knative:main Oct 8, 2025
36 checks passed
@dprotaso
Copy link
Member

dprotaso commented Oct 8, 2025

thanks @qswinson 🎉

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test-and-release Test infrastructure, tests or release lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

eks use aws web identity token for SQS queue

5 participants