[bitnami/spring-cloud-dataflow] Release 2.11.1-debian-11-r4 (#54693)
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
GitHub
parent
90d03a55c5
commit
c1a48deae3
|
|
@ -8,10 +8,10 @@ ARG TARGETARCH
|
|||
|
||||
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
|
||||
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
|
||||
org.opencontainers.image.created="2024-01-06T10:47:54Z" \
|
||||
org.opencontainers.image.created="2024-01-11T15:49:40Z" \
|
||||
org.opencontainers.image.description="Application packaged by VMware, Inc" \
|
||||
org.opencontainers.image.licenses="Apache-2.0" \
|
||||
org.opencontainers.image.ref.name="2.11.1-debian-11-r3" \
|
||||
org.opencontainers.image.ref.name="2.11.1-debian-11-r4" \
|
||||
org.opencontainers.image.title="spring-cloud-dataflow" \
|
||||
org.opencontainers.image.vendor="VMware, Inc." \
|
||||
org.opencontainers.image.version="2.11.1"
|
||||
|
|
@ -28,7 +28,7 @@ RUN install_packages ca-certificates curl procps zlib1g
|
|||
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
|
||||
COMPONENTS=( \
|
||||
"java-17.0.9-11-6-linux-${OS_ARCH}-debian-11" \
|
||||
"yq-4.40.5-0-linux-${OS_ARCH}-debian-11" \
|
||||
"yq-4.40.5-1-linux-${OS_ARCH}-debian-11" \
|
||||
"spring-cloud-dataflow-2.11.1-0-linux-${OS_ARCH}-debian-11" \
|
||||
) ; \
|
||||
for COMPONENT in "${COMPONENTS[@]}"; do \
|
||||
|
|
|
|||
|
|
@ -15,6 +15,6 @@
|
|||
"arch": "amd64",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "4.40.5-0"
|
||||
"version": "4.40.5-1"
|
||||
}
|
||||
}
|
||||
|
|
@ -66,9 +66,31 @@ docker build -t bitnami/APP:latest .
|
|||
|
||||
## Configuration
|
||||
|
||||
You can use some environment variable in order to configure the deployment of spring cloud data flow.
|
||||
### Environment variables
|
||||
|
||||
### Configuring database
|
||||
| Name | Description | Default Value | Can be set |
|
||||
|------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------|
|
||||
| `$SPRING_CLOUD_DATAFLOW_BASE_DIR` | Base path for SPRING CLOUD DATAFLOW files. | `${BITNAMI_ROOT_DIR}/spring-cloud-dataflow` | |
|
||||
| `$SPRING_CLOUD_DATAFLOW_VOLUME_DIR` | SPRING CLOUD DATAFLOW directory for persisted files. | `${BITNAMI_VOLUME_DIR}/spring-cloud-dataflow` | |
|
||||
| `$SPRING_CLOUD_DATAFLOW_CONF_DIR` | SPRING CLOUD DATAFLOW configuration directory. | `${SPRING_CLOUD_DATAFLOW_BASE_DIR}/conf` | |
|
||||
| `$SPRING_CLOUD_DATAFLOW_CONF_FILE` | Main SPRING CLOUD DATAFLOW configuration file. | `${SPRING_CLOUD_DATAFLOW_CONF_DIR}/application.yml` | |
|
||||
| `$SPRING_CLOUD_DATAFLOW_M2_DIR` | SPRING CLOUD DATAFLOW maven root dir. | `/.m2` | |
|
||||
| `$SPRING_CLOUD_DATAFLOW_DAEMON_USER` | Users that will execute the SPRING CLOUD DATAFLOW Server process. | `dataflow` | |
|
||||
| `$SPRING_CLOUD_DATAFLOW_DAEMON_GROUP` | Group that will execute the SPRING CLOUD DATAFLOW Server process. | `dataflow` | |
|
||||
| `$SERVER_PORT` | Custom port number to use for the SPRING CLOUD DATAFLOW Server service. | | ✓ |
|
||||
| `$SPRING_CLOUD_CONFIG_ENABLED` | Whether to load config using Spring Cloud Config Servie. | `false` | ✓ |
|
||||
| `$SPRING_CLOUD_KUBERNETES_SECRETS_ENABLE_API` | Whether to load config using Kubernetes API. | `false` | ✓ |
|
||||
| `$SPRING_CLOUD_KUBERNETES_CONFIG_NAME` | Name of the ConfigMap that contains the configuration. | | ✓ |
|
||||
| `$SPRING_CLOUD_KUBERNETES_SECRETS_PATHS` | Paths where the secrets are going to be mount. | | ✓ |
|
||||
| `$SPRING_CLOUD_DATAFLOW_FEATURES_STREAMS_ENABLED` | Whether enable stream feature in dataflow. It need SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | `false` | ✓ |
|
||||
| `$SPRING_CLOUD_DATAFLOW_FEATURES_TASKS_ENABLED` | Whether enable tasks feature in dataflow. It need SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | `false` | ✓ |
|
||||
| `$SPRING_CLOUD_DATAFLOW_FEATURES_SCHEDULES_ENABLED` | Whether enable schedules feature in dataflow. It need SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | `false` | ✓ |
|
||||
| `$SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI` | Skipper server URI | | ✓ |
|
||||
| `$SPRING_CLOUD_DATAFLOW_TASK_COMPOSEDTASKRUNNER_URI` | Workaround for https://github.com/spring-cloud/spring-cloud-dataflow/issues/5072 | `maven://org.springframework.cloud:spring-cloud-dataflow-composed-task-runner:${APP_VERSION:-}` | ✓ |
|
||||
| `$JAVA_OPTS` | JVM options | | ✓ |
|
||||
|
||||
|
||||
#### Configuring database
|
||||
|
||||
A relational database is used to store stream and task definitions as well as the state of executed tasks. Spring Cloud Data Flow provides schemas for H2, MySQL, Oracle, PostgreSQL, Db2, and SQL Server. Use the following environment to configure the connection.
|
||||
|
||||
|
|
@ -77,7 +99,7 @@ A relational database is used to store stream and task definitions as well as th
|
|||
* SPRING_DATASOURCE_PASSWORD=bn_dataflow
|
||||
* SPRING_DATASOURCE_DRIVER_CLASS_NAME=org.mariadb.jdbc.Driver
|
||||
|
||||
### Configuring additional features
|
||||
#### Configuring additional features
|
||||
|
||||
Spring Cloud Data Flow Server offers specific set of features that can be enabled/disabled when launching.
|
||||
|
||||
|
|
@ -86,7 +108,7 @@ Spring Cloud Data Flow Server offers specific set of features that can be enable
|
|||
|
||||
In the same way, you might need to customize the JVM. Use the `JAVA_OPTS` environment variable for this purpose.
|
||||
|
||||
### Configuring stream platform
|
||||
#### Configuring stream platform
|
||||
|
||||
In order to deploy streams using data flow you will require [Spring Cloud Skipper](https://github.com/bitnami/containers/blob/main/bitnami/spring-cloud-skipper) and one of the following messaging platforms. Please add the following environment variable to point to a different skipper endpoint.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue