andormarkus opened a new issue #19372:
URL: https://github.com/apache/airflow/issues/19372
### Apache Airflow Provider(s)
amazon
### Versions of Apache Airflow Providers
apache-airflow-providers-amazon==2.3.0
### Apache Airflow version
2.1.4 (latest released)
### Operating System
Amazon Linux 2
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
_No response_
### What happened
Adding extra kwargs to EKSCreateNodegroupOperator brokes the DAG.
```shell
Broken DAG: [/opt/airflow/dags/maintenance_deltatable_compaction.py]
Traceback (most recent call last):
File
"/home/airflow/.local/lib/python3.9/site-packages/airflow/models/baseoperator.py",
line 188, in apply_defaults
result = func(self, *args, **kwargs)
File
"/home/airflow/.local/lib/python3.9/site-packages/airflow/models/baseoperator.py",
line 535, in __init__
raise AirflowException(
airflow.exceptions.AirflowException: Invalid arguments were passed to
EKSCreateNodegroupOperator (task_id: create_eks_nodegroup). Invalid arguments
were:
**kwargs: {'amiType': 'BOTTLEROCKET_x86_64', 'instanceTypes': 't3.large',
'capacityType': 'ON_DEMAND'}
```
### What you expected to happen
I should be able to pass all the kwargs which are available in boto3 into
EKS operator.
### How to reproduce
```python
create_nodegroup = EKSCreateNodegroupOperator(
task_id='create_eks_nodegroup',
cluster_name=cluster_name,
nodegroup_name=node_group_name,
nodegroup_subnets=get_subnets(),
nodegroup_role_arn=get_node_role(),
amiType = "BOTTLEROCKET_x86_64",
instanceTypes = "t3.large",
capacityType = "ON_DEMAND"
)
````
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] 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)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
