EKSPodOperator doesnt use AWS Connection
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Apache Airflow version
2.11.0
### If "Other Airflow 2/3 version" selected, which one?
_No response_
### What happened?
Tried using an AWS Connection with EKSPodOperator and it didn't work. Tried setting the environment vars and it did work.
### What you think should happen instead?
Using an AWS Connection should work for the EKSPodOperator
### How to reproduce
Set up and AWS EKS connection.
Try using EKSPodOperator
### Operating System
Mac
### Versions of Apache Airflow Providers
_No response_
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
Nothing relevant.
### Anything else?
_No response_
### Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start by locating EKSPodOperator and the AWS Connection handling it uses, then compare that path with the environment-variable configuration described in the report. Reproduce the issue with an AWS EKS connection and the official Apache Airflow Helm Chart; done means EKSPodOperator works without requiring AWS environment variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, python
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100