Corneil du Plessis
Corneil du Plessis
@VikasMGowda05 There is no direct property in the values file. Adding the appropriate environmental variable will ensure the value is set for the deployment platform. ```yaml server: configuration: extraEnvVars: name:...
> **Description:** We have seen the SCDF document which says we can set the property maximumConcurrentTasks as below > > spring.cloud.dataflow.task.platform..accounts[].deployment.maximumConcurrentTasks` > > but while installing the SCDF using helm...
default is the account name. The deployment option is only for Cloud Foundry.
You can add more accounts if you target other namespaces or clusters
@VikasMGowda05 Please try: ```yaml server: extraEnvVars: - name: 'SPRING_CLOUD_DATAFLOW_TASK_PLATFORM_KUBERNETES_ACCOUNTS_DEFAULT_MAXIMUMCONCURRENTTASKS' value: 100 ```
I would also like to offer some help. I have had a good experience using OpenRewrite recipes to upgrade projects.
I would suggest using latest releases: ```shell export DATAFLOW_VERSION=2.11.5 export SKIPPER_VERSION=2.11.5 ./dc.sh kafka mysql prometheus up ```
You are using snapshot builds. Why don't you use a release build?
I believe there are `podAnnotations` in the Bitnami Helm values schema. You can set different for skipper stream deployments and dataflow task launches.
It seems like the Bitnami Helm chart doesn't provide for adding a generic block of configuration for dataflow or skipper like we do in our Carvel deployment. The plain kubernetes...