[
https://issues.apache.org/jira/browse/SPARK-57900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kousuke Saruta updated SPARK-57900:
-----------------------------------
Description:
This sub-task is part of the umbrella
[SPARK-57703|https://issues.apache.org/jira/browse/SPARK-57703] (OIDC
Credential Propagation).
h2. Problem
We need to verify the full flow (token ingestion -> STS -> S3A read/write ->
credential refresh) in a realistic Kubernetes environment.
h2. Goal
An optional end-to-end test that validates the entire credential propagation
pipeline.
h2. Scope
* Behind Maven profile {{-Poidc-e2e}} (skipped by default in CI)
* Projected ServiceAccount token -> {{AwsStsCredentialProvider}} -> LocalStack
STS -> S3A read/write
* Token rotation mid-job triggers credential refresh and continued S3 access
* Requires Minikube and S3 compatible storage
h2. Acceptance criteria
* A Spark job on Minikube reads/writes S3 (LocalStack) using OIDC-derived
credentials.
* Mid-job token rotation results in successful credential refresh (no S3 access
failures).
* Test is skipped when profile is not active.
* Setup instructions are documented.
Reference: [SPIP design document Testing
plan|https://docs.google.com/document/d/1usJKncCPMiyFUg7aIdpZ0HQsklXIHow_sU_6dfFMjN0/edit].
was:
This sub-task is part of the umbrella
[SPARK-57703|https://issues.apache.org/jira/browse/SPARK-57703] (OIDC
Credential Propagation).
h2. Problem
We need to verify the full flow (token ingestion -> STS -> S3A read/write ->
credential refresh) in a realistic Kubernetes environment.
h2. Goal
An optional end-to-end test that validates the entire credential propagation
pipeline.
h2. Scope
* Behind Maven profile {{-Poidc-e2e}} (skipped by default in CI)
* Projected ServiceAccount token -> {{AwsStsCredentialProvider}} -> LocalStack
STS -> S3A read/write
* Token rotation mid-job triggers credential refresh and continued S3 access
* Requires Minikube and LocalStack
h2. Acceptance criteria
* A Spark job on Minikube reads/writes S3 (LocalStack) using OIDC-derived
credentials.
* Mid-job token rotation results in successful credential refresh (no S3 access
failures).
* Test is skipped when profile is not active.
* Setup instructions are documented.
Reference: [SPIP design document Testing
plan|https://docs.google.com/document/d/1usJKncCPMiyFUg7aIdpZ0HQsklXIHow_sU_6dfFMjN0/edit].
> Add E2E test with Minikube and S3 compatible storage
> ----------------------------------------------------
>
> Key: SPARK-57900
> URL: https://issues.apache.org/jira/browse/SPARK-57900
> Project: Spark
> Issue Type: Sub-task
> Components: Kubernetes, Tests
> Affects Versions: 4.3.0
> Reporter: Kousuke Saruta
> Priority: Major
>
> This sub-task is part of the umbrella
> [SPARK-57703|https://issues.apache.org/jira/browse/SPARK-57703] (OIDC
> Credential Propagation).
> h2. Problem
> We need to verify the full flow (token ingestion -> STS -> S3A read/write ->
> credential refresh) in a realistic Kubernetes environment.
> h2. Goal
> An optional end-to-end test that validates the entire credential propagation
> pipeline.
> h2. Scope
> * Behind Maven profile {{-Poidc-e2e}} (skipped by default in CI)
> * Projected ServiceAccount token -> {{AwsStsCredentialProvider}} ->
> LocalStack STS -> S3A read/write
> * Token rotation mid-job triggers credential refresh and continued S3 access
> * Requires Minikube and S3 compatible storage
> h2. Acceptance criteria
> * A Spark job on Minikube reads/writes S3 (LocalStack) using OIDC-derived
> credentials.
> * Mid-job token rotation results in successful credential refresh (no S3
> access failures).
> * Test is skipped when profile is not active.
> * Setup instructions are documented.
> Reference: [SPIP design document Testing
> plan|https://docs.google.com/document/d/1usJKncCPMiyFUg7aIdpZ0HQsklXIHow_sU_6dfFMjN0/edit].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
