You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can run or debug the `FlinkOperator` from your preferred IDE. The operator itself is accessing the deployed Flink clusters through the REST interface. When running locally the `rest.port`, `rest.address` and `kubernetes.rest-service.exposed.type` Flink configuration parameters must be modified.
79
88
80
89
When using `minikube tunnel` the rest service is exposed on `localhost:8081`
Due to fabric8 conflicts between core Flink and the operator, the `flink-kubernetes-operator` module depends on the shaded `flink-kubernetes-standalone` jar which contains the relocated version of the old fabric8 Kubernetes client. Unfortunately IntelliJ is not great at handling dependencies with classifiers so you might get the following error when trying to run `FlinkOperator#main`:
There are two solutions to this problem, both requires you to first build the project.
113
+
114
+
First:
115
+
98
116
```bash
99
-
helm uninstall flink-kubernetes-operator
117
+
mvn clean install
100
118
```
101
119
120
+
Then either:
121
+
122
+
1. Import the `flink-kubernetes-operator` submodule as a separate IntelliJ project. This will resolve the classifier dependency correctly from your local maven cache.
123
+
2. If you want to keep a single multi-module project, you need to add the `flink-kubernetes-standalone-XX-shaded.jar` on the classpath manually when running the main method:
124
+
`Edit Run Configuration/Modify Options/Modify Classpath`
125
+
102
126
### Generating and Upgrading the CRD
103
127
104
128
By default, the CRD is generated by the [Fabric8 CRDGenerator](https://github.com/fabric8io/kubernetes-client/blob/master/doc/CRD-generator.md), when building from source.
We use [GitHub Actions](https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions) to help you automate your software development workflows in the same place you store code and collaborate on pull requests and issues.
123
148
You can write individual tasks, called actions, and combine them to create a custom workflow.
124
149
Workflows are custom automated processes that you can set up in your repository to build, test, package, release, or deploy any code project on GitHub.
0 commit comments