Files
deprecated-helm-charts/stable/spring-cloud-data-flow/values.yaml
T
Chris SchaeferandKubernetes Prow Robot d3eb35acd6 [stable/spring-cloud-data-flow] Updates for Spring Cloud Data Flow 2.0 (#12285)
- Single server consolidations
- Update Skipper to 2.0
- Remove metrics
- Add ability to use Kafka or RabbitMQ
- Remove deprecated functionality

Signed-off-by: Chris Schaefer <cschaefer@pivotal.io>
2019-03-18 02:27:23 -07:00

68 lines
1.4 KiB
YAML

# Default values for spring-cloud-data-flow.
rbac:
# Specifies whether RBAC resources should be created
create: true
serviceAccount:
# Specifies whether a service account should be created
create: true
# The name of the service account to use.
# If not set and create is true, a name is generated using the serviceAccountName template
name:
server:
image: springcloud/spring-cloud-dataflow-server
version: 2.0.1.RELEASE
imagePullPolicy: IfNotPresent
platformName: default
service:
type: LoadBalancer
externalPort: 80
resources: {}
# limits:
# cpu: 1.0
# memory: 2048Mi
# requests:
# cpu: 0.5
# memory: 640Mi
skipper:
image: springcloud/spring-cloud-skipper-server
version: 2.0.0.RELEASE
imagePullPolicy: IfNotPresent
platformName: default
service:
type: ClusterIP
resources: {}
# limits:
# cpu: 1.0
# memory: 1024Mi
# requests:
# cpu: 0.5
# memory: 640Mi
deployer:
resourceLimits:
cpu: 500m
memory: 1024Mi
readinessProbe:
initialDelaySeconds: 120
livenessProbe:
initialDelaySeconds: 90
rabbitmq:
enabled: true
rabbitmqUsername: user
kafka:
enabled: false
replicas: 1
configurationOverrides:
"offsets.topic.replication.factor": 1
"confluent.support.metrics.enable": false
zookeeper:
replicaCount: 1
mysql:
mysqlDatabase: dataflow