chethanuk-plutoflume opened a new pull request, #26664: URL: https://github.com/apache/airflow/pull/26664
<!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: related: #9134 How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> Adding new Flink on K8s Operator to cncf provider NOTE: The [Flink Kubernetes Operator](https://github.com/apache/flink-kubernetes-operator) extends the [Kubernetes](https://kubernetes.io/) API with the ability to manage and operate Flink Deployments. The operator features the following amongst others: Basically allows users to manage Flink applications and their lifecycle through native k8s tooling <img alt="Operator Overview" width="100%" src="https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/img/overview.svg"> - Deploy and monitor Flink Application and Session deployments - Upgrade, suspend and delete deployments - Full logging and metrics integration - Flexible deployments and native integration with Kubernetes tooling --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
