This contains examples showing applications that produce a docker image which is compatible with the Flink operator. Please use these examples as a reference while building applications to be be executed by the flink operator.
- The Flink operator custom resource contains image field, and expects the image to have both flink and application code to be packaged in it.
- The operator starts up Jobmanager and Taskmanager pods using Container Args.
- The operator submits the flink job through the REST API in the Jobmanager. For this to work, the jar file of the application needs to be present in the folder as indicated by the config value web.upload.dir.
- The operator injects flink configuration through environment variables.
- If there are issues in the image that causes either pods to restart, or Flink cluster to not respond to REST API requests, the state machine will not transition beyond the READY state.