Application Manager supports Flink 1.7 and manages Flink applications using the container entrypoint. This makes the deployment of applications more robust and less time consuming. Instead of requiring Application Manager to access and submit your JAR artifact to Flink, we let Flink fetch it.
You can now configure custom imagePullSecrets for each Deployment, making it possible to access custom Docker registries.
The Settings page of the web user interface now allows you to manage more resources, such as namespaces, API tokens, and secret values.
Important: Flink 1.7 jobs require entryClass to be configured in Deployment.spec.template.spec.artifact. If you are running Application Manager version greater or equal to 1.3.2 and Flink image tagged as 1.7.0-dap2 or 1.7.1-dap2 (or more recent) this requirement has been dropped. See release notes of version 1.3.2.
If you are using Flink 1.6, please set your Flink applications to use the image with tag: registry.platform.data-artisans.net/trial/v1.3/flink:1.6.2-dap2-scala_2.11. The dap2 image fixes the built-in InfluxDB metrics reporter that was included in earlier versions. For Flink 1.7, all images already contain the fixed metrics reporter.
In order to use an existing data volume of an earlier installation please add the following securityContext entry to your Application Manager Deployment:
Deployment.spec.startFromSavepoint has been deprecated in favor of Deployment.spec.restoreStrategy. Operations against startFromSavepoint are reflected in restoreStrategy and vice versa. Only when using the new LATEST_STATE restore strategy will startFromSavepoint be not available.