Skip to content

Commit 6144738

Browse files
authored
Merge pull request #50 from sachingade20/review-comments-fixes
Review comments fixes
2 parents 5336277 + ccb2e24 commit 6144738

File tree

2 files changed

+218
-0
lines changed

2 files changed

+218
-0
lines changed
Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
clusteredMode: false
2+
3+
##---------------------------------------------
4+
## Flow storage configuration section
5+
##---------------------------------------------
6+
7+
storage:
8+
volumes:
9+
serverPlugins:
10+
name: flow-server-shared
11+
accessMode: ReadWriteMany
12+
## A ReadWriteMany storage class used for plugins directory.
13+
## It is shared across all the Flow server and the web server
14+
## replicas.
15+
storageClass: nfs-client
16+
# In order to use any existing pvc. set existingClaim flag to true and
17+
# set storage.volumes.serverPlugins.name to pvc name
18+
existingClaim: false
19+
repositoryStorage:
20+
storage: 10Gi
21+
22+
##---------------------------------------------
23+
## Flow components/workloads configuration section
24+
##---------------------------------------------
25+
server:
26+
resources:
27+
limits:
28+
cpu: 1.5
29+
requests:
30+
cpu: 0.5
31+
32+
#---------------------------------------------
33+
# Flow DevOps Insight configuration section
34+
#---------------------------------------------
35+
36+
dois:
37+
openshiftNodeTuning: true
38+
sysctlInitContainer:
39+
enabled: false
40+
41+
#---------------------------------------------
42+
# Volume configuration section
43+
#---------------------------------------------
44+
volumePermissions:
45+
enabled: false
46+
47+
#---------------------------------------------
48+
# Ingress configuration section
49+
#---------------------------------------------
50+
ingress:
51+
# Whether to create an OpenShift Route rather than a generic Ingress.
52+
route: true
53+
54+
# Install mariadb chart for demo mode
55+
# and create a database and user for Flow to use.
56+
# Note that the database user name and password
57+
# specified in the `initdbScripts` section must
58+
# match the values in the `database` section below.
59+
60+
mariadb:
61+
enabled: true
62+
db:
63+
user: "flow"
64+
volumePermissions:
65+
enabled: false
66+
securityContext:
67+
enabled: false
68+
69+
70+
database:
71+
dbName: "demo"
72+
dbUser: "flow"
73+
dbType: "mariadb"
74+
dbPort: 3306
75+
clusterEndpoint: "mariadb"
76+
# externalEndpoint: ""
77+
78+
##---------------------------------------------
79+
## Flow server admin credentials section
80+
##---------------------------------------------
81+
82+
flowCredentials:
83+
## Name of the secret containing the admin user password to use. If set, the admin user password
84+
## will be read from the secret instead of the plain-text `adminPassword` (not recommended for production).
85+
##
86+
## The data field must contain base64 encoded value for key 'CBF_SERVER_ADMIN_PASSWORD'.
87+
## E.g., kubectl create secret generic flow-admin-secret --from-literal=CBF_SERVER_ADMIN_PASSWORD='rrx!*d$z75Dsb'
88+
##
89+
## Uncomment the following line to set the name of the secret to use to read the admin user password.
90+
# existingSecret: flow-admin-secret
91+
##
92+
## IMPORTANT: This is clearly not meant for production use and is only meant for demo environments
93+
## where security may not be a concern. Use of `existingSecret` is preferred.
94+
adminPassword:
95+
96+
#---------------------------------------------
97+
# Flow ingress configuration section
98+
# OCP Uses routes so nginx-ingress should be disabled
99+
#---------------------------------------------
100+
nginx-ingress:
101+
enabled: false
Lines changed: 117 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
##---------------------------------------------
2+
## Database configuration section
3+
##---------------------------------------------
4+
database:
5+
## 1. The database to use for CloudBees Flow installation.
6+
## The following database types are supported with Flow in a production environment:
7+
## mysql, oracle, or sqlserver
8+
##
9+
## The database type must be specified.
10+
dbType:
11+
12+
## 2. The name of the database to use with CloudBees Flow installation.
13+
##
14+
## The database name must be specified.
15+
dbName:
16+
17+
## 3. Name of the secret containing the database user credentials.
18+
## The data field must contain base64 encoded values for keys 'DB_USER' and 'DB_PASSWORD'.
19+
## E.g., kubectl create secret generic flow-db-secret --from-literal=DB_USER=flow_user --from-literal=DB_PASSWORD='S!*d$z5Dsb'
20+
##
21+
## Set the name of the secret that contains the database user credentials.
22+
existingSecret: flow-db-secret
23+
24+
## 4.(a) Database hostname if the database instance is running outside the cluster
25+
##
26+
## Either the database hostname (externalEndpoint) or the database service name (clusterEndpoint) must be specified.
27+
##
28+
## Uncomment the following line to set the database hostname.
29+
# externalEndpoint: flowdb.example.com
30+
31+
## 4.(b) Database service name if the database instance is running within the cluster. Use the service DNS name if
32+
## the database service is running in a different namespace in the cluster, e.g., my-sql-db-mysql.default.svc.cluster.local
33+
##
34+
## Either the database hostname (externalEndpoint) or the database service name (clusterEndpoint) must be specified.
35+
##
36+
## Uncomment the following line to set the database service name.
37+
# clusterEndpoint: flow-db-mysql
38+
39+
## 5. The database port to use.
40+
##
41+
## The database port must be specified.
42+
dbPort:
43+
44+
# External Mysql Connector URL to download during cloudbees flow installation
45+
mysqlConnector:
46+
externalUrl:
47+
48+
#---------------------------------------------
49+
# Ingress configuration section
50+
#---------------------------------------------
51+
ingress:
52+
# Whether to create an OpenShift Route rather than a generic Ingress.
53+
route: true
54+
55+
##---------------------------------------------
56+
## Flow storage configuration section
57+
##---------------------------------------------
58+
storage:
59+
volumes:
60+
serverPlugins:
61+
name: flow-server-shared
62+
accessMode: ReadWriteMany
63+
## A ReadWriteMany storage class used for plugins directory.
64+
## It is shared across all the Flow server and the web server
65+
## replicas.
66+
storageClass: nfs-client
67+
# In order to use any existing pvc. set existingClaim flag to true and
68+
# set storage.volumes.serverPlugins.name to pvc name
69+
existingClaim: true
70+
71+
72+
##---------------------------------------------
73+
## Flow server admin credentials section
74+
##---------------------------------------------
75+
76+
flowCredentials:
77+
## Name of the secret containing the admin user password to use.
78+
## The data field must contain base64 encoded value for key 'CBF_SERVER_ADMIN_PASSWORD'.
79+
## E.g., kubectl create secret generic your-flow-admin-secret --from-literal=CBF_SERVER_ADMIN_PASSWORD='rrx!*d$z75Dsb'
80+
##
81+
## Set the name of the secret that contains the admin user password.
82+
existingSecret:
83+
84+
#---------------------------------------------
85+
# Flow DevOps Insight configuration section
86+
#---------------------------------------------
87+
88+
dois:
89+
openshiftNodeTuning: true
90+
sysctlInitContainer:
91+
enabled: false
92+
93+
#---------------------------------------------
94+
# Volume configuration section
95+
#---------------------------------------------
96+
volumePermissions:
97+
enabled: false
98+
99+
#---------------------------------------------
100+
# Zookeeper configuration section
101+
#---------------------------------------------
102+
# Keep fsGroup and runAsUser empty so OCP will assign random user/group
103+
zookeeper:
104+
securityContext:
105+
fsGroup:
106+
runAsUser:
107+
image:
108+
repository: cbflowtest/zookeeper # Container image repository for zookeeper container.
109+
tag: 3.6.2
110+
111+
#---------------------------------------------
112+
# Flow ingress configuration section
113+
# OCP Uses routes so nginx-ingress should be disabled
114+
#---------------------------------------------
115+
nginx-ingress:
116+
enabled: false
117+

0 commit comments

Comments
 (0)