airflow.providers.amazon.aws.sensors.eks
¶
Tracking the state of Amazon EKS Clusters, Amazon EKS managed node groups, and AWS Fargate profiles.
Module Contents¶
Classes¶
Check the state of an Amazon EKS Cluster until it reaches the target state or another terminal state. |
|
Check the state of an AWS Fargate profile until it reaches the target state or another terminal state. |
|
Check the state of an EKS managed node group until it reaches the target state or another terminal state. |
Attributes¶
- airflow.providers.amazon.aws.sensors.eks.UNEXPECTED_TERMINAL_STATE_MSG = Terminal state reached. Current state: {current_state}, Expected state: {target_state}[source]¶
- class airflow.providers.amazon.aws.sensors.eks.EksClusterStateSensor(*, cluster_name, target_state=ClusterStates.ACTIVE, aws_conn_id=DEFAULT_CONN_ID, region=None, **kwargs)[source]¶
Bases:
airflow.sensors.base.BaseSensorOperator
Check the state of an Amazon EKS Cluster until it reaches the target state or another terminal state.
See also
For more information on how to use this sensor, take a look at the guide: Wait on an Amazon EKS cluster state
- Parameters
cluster_name (str) – The name of the Cluster to watch. (templated)
target_state (airflow.providers.amazon.aws.hooks.eks.ClusterStates) – Target state of the Cluster. (templated)
region (str | None) – Which AWS region the connection should use. (templated) If this is None or empty then the default boto3 behaviour is used.
aws_conn_id (str) – The Airflow connection used for AWS credentials. (templated) If this is None or empty then the default boto3 behaviour is used. If running Airflow in a distributed manner and aws_conn_id is None or empty, then the default boto3 configuration would be used (and must be maintained on each worker node).
- class airflow.providers.amazon.aws.sensors.eks.EksFargateProfileStateSensor(*, cluster_name, fargate_profile_name, target_state=FargateProfileStates.ACTIVE, aws_conn_id=DEFAULT_CONN_ID, region=None, **kwargs)[source]¶
Bases:
airflow.sensors.base.BaseSensorOperator
Check the state of an AWS Fargate profile until it reaches the target state or another terminal state.
See also
For more information on how to use this sensor, take a look at the guide: Wait on an AWS Fargate profile state
- Parameters
cluster_name (str) – The name of the Cluster which the AWS Fargate profile is attached to. (templated)
fargate_profile_name (str) – The name of the Fargate profile to watch. (templated)
target_state (airflow.providers.amazon.aws.hooks.eks.FargateProfileStates) – Target state of the Fargate profile. (templated)
region (str | None) – Which AWS region the connection should use. (templated) If this is None or empty then the default boto3 behaviour is used.
aws_conn_id (str) – The Airflow connection used for AWS credentials. (templated) If this is None or empty then the default boto3 behaviour is used. If running Airflow in a distributed manner and aws_conn_id is None or empty, then the default boto3 configuration would be used (and must be maintained on each worker node).
- class airflow.providers.amazon.aws.sensors.eks.EksNodegroupStateSensor(*, cluster_name, nodegroup_name, target_state=NodegroupStates.ACTIVE, aws_conn_id=DEFAULT_CONN_ID, region=None, **kwargs)[source]¶
Bases:
airflow.sensors.base.BaseSensorOperator
Check the state of an EKS managed node group until it reaches the target state or another terminal state.
See also
For more information on how to use this sensor, take a look at the guide: Wait on an Amazon EKS managed node group state
- Parameters
cluster_name (str) – The name of the Cluster which the Nodegroup is attached to. (templated)
nodegroup_name (str) – The name of the Nodegroup to watch. (templated)
target_state (airflow.providers.amazon.aws.hooks.eks.NodegroupStates) – Target state of the Nodegroup. (templated)
region (str | None) – Which AWS region the connection should use. (templated) If this is None or empty then the default boto3 behaviour is used.
aws_conn_id (str) – The Airflow connection used for AWS credentials. (templated) If this is None or empty then the default boto3 behaviour is used. If running Airflow in a distributed manner and aws_conn_id is None or empty, then the default boto3 configuration would be used (and must be maintained on each worker node).