Flink cluster
Requirements
Flex requires at least one configured Flink cluster to operate.
Compatibility
Flex is compatible with v1 of the Flink REST API.
Support for other managed services (such as Amazon Managed Service for Apache Flink) is coming soon. Please contact us if this is a priority for your organization.
Configuration
| Variable | Required | Description |
|---|---|---|
| FLINK_REST_URL | True | The Flink REST API endpoint to connect to. For example: http://localhost:8081 |
| FLINK_ENVIRONMENT_NAME | False | Optional, UI friendly label for the cluster and its resources |
| FLINK_TIMEOUT_MS | False | The timeout value in ms for all HTTP requests made to a Flink cluster. Default: 5000 |
| FLINK_PERMISSIVE_SSL | False | True if SSL certificate validation should be disabled. Default: false |
Multi cluster
Flex will manage as many clusters as your license permits - you may have to increase the memory and CPU to ensure that the regular snapshotting process executes within thirty seconds.
To configure multiple clusters, simply repeat the connection configuration with _2, _3, _4 suffixes.
FLINK_ENVIRONMENT_NAME for each resource-set is displayed in the Flex UI when switching cluster.
The sort order in the UI is controlled by these numeric suffixes.
# Cluster 1 (Staging)
FLINK_REST_URL=https://flink-staging.corp:8081
FLINK_ENVIRONMENT_NAME="Flink Staging"
# Cluster 2 (Production)
FLINK_REST_URL_2=https://flink-prod.corp:8081
FLINK_TIMEOUT_MS_2=7000
FLINK_ENVIRONMENT_NAME_2="Flink Production"
Access control
User permissions to Flink cluster resources are defined by Flink actions. See User Authorization for more details.