SameerMesiah97 commented on PR #71244: URL: https://github.com/apache/airflow/pull/71244#issuecomment-5431124948
> Although this can be implemented with `BashOperator` and `kubectl exec`, that moves additional integration logic to every user: installing and maintaining `kubectl` on the workers, distributing kubeconfig and cloud authentication helpers, handling shell quoting, and mapping Kubernetes errors and output into Airflow. This operator provides that behavior through `KubernetesHook` and Airflow connections. The provider already uses the `pods/exec` API internally, so this is not a new Kubernetes mechanism. I think this is the strongest argument here. If using this operator saves time and effort for users who want this specific functionality, then I believe it is justified. But like I mentioned above, why only `exec`? Why not other commands like `log` or `watch`? It seems premature and restrictive to narrow it to just `exec`? -- 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]
