Skip to content

Commit 48fe7da

Browse files
pattyhairpattyhair
committed
[NMB-28832] Add sample values files for Flow on Kubernetes.
1 parent 90dc713 commit 48fe7da

6 files changed

Lines changed: 1357 additions & 2 deletions

File tree

‎README.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
## Welcome
2-
Welcome to the CloudBees examples repository. This repository was created as a place for storing tutorials, examples, and other learning materials.
2+
Welcome to the CloudBees examples repository. This repository was created as a place for storing tutorials, examples, and other learning materials.
33

44
## Examples summary
5-
The following table is a brief summary of each of the example projects.
5+
The following table is a brief summary of each of the example projects.
66

77
|Directory|Description |
88
|:---|:-|
99
|pipeline-template-examples|This repository includes a sample Pipeline Template Catalog. The demos folder includes examples of how to customize a template.yaml file. |
1010
|helm-custom-value-file-examples|Custom Property Value Files for the CloudBees Core for Modern Platforms Helm installation.|
11+
|flow-on-kubernetes|Sample property value files for CloudBees Flow on Kubernetes Helm installation.|

‎flow-on-kubernetes/README.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# CloudBees Flow Installation Examples
2+
3+
## Introduction
4+
These YAML files are example values files for the CloudBees Flow Helm Chart.
5+
6+
## Examples
7+
- `cloudbees-flow-demo.yaml`: Example .yaml file for installing CloudBees Flow on standard Kubernetes for a non-production environment.
8+
- `cloudbees-flow-prod.yaml`: Example .yaml file for installing CloudBees Flow on standard Kubernetes for a production environment.
9+
- `values.yaml`: Default parameter values for CloudBees Flow on standard Kubernetes. Springboard from this file to create your own custom values.yaml file.
10+
- `values-filebeat.yaml`: Sample values file to configure Filebeat log shipper to capture logs from CloudBees Flow services and pods.

‎flow-on-kubernetes/cloudbees-flow-demo.yaml‎

Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
demoMode: true
2+
3+
##---------------------------------------------
4+
## Flow storage configuration section
5+
##---------------------------------------------
6+
7+
storage:
8+
volumes:
9+
serverPlugins:
10+
accessMode: ReadWriteOnce
11+
# Storage class for plugins directory. Currently it has to be shared across server and web replicas.
12+
# Server and web are co-located using hard affinity rule for demoMode. StorageClass is null here to ensure the same behavior across all cloud providers
13+
# (it forces storage class to fall back to "default" disk based ReadWriteOnce platform specific storage class)
14+
storageClass: null
15+
storage: 5Gi
16+
17+
repositoryStorage:
18+
storage: 10Gi
19+
20+
##---------------------------------------------
21+
## Flow components/workloads configuration section
22+
##---------------------------------------------
23+
server:
24+
resources:
25+
limits:
26+
cpu: 1.5
27+
requests:
28+
cpu: 0.5
29+
30+
# No zookeeper for demo mode
31+
zookeeper:
32+
enabled: false
33+
34+
# Install mariadb chart for demo mode
35+
# and create a database and user for Flow to use.
36+
# Note that the database user name and password
37+
# specified in the `initdbScripts` section must
38+
# match the values in the `database` section below.
39+
40+
mariadb:
41+
fullnameOverride: mariadb
42+
replication:
43+
enabled: false
44+
securityContext:
45+
enabled: true
46+
volumePermissions:
47+
enabled: true
48+
initdbScripts:
49+
demo-db.sql: |-
50+
CREATE DATABASE IF NOT EXISTS demo CHARACTER SET utf8 COLLATE utf8_unicode_ci;
51+
CREATE DATABASE IF NOT EXISTS demo_upgrade CHARACTER SET utf8 COLLATE utf8_unicode_ci;
52+
CREATE USER 'flow'@'%' IDENTIFIED BY 'flow_pass';
53+
GRANT ALL PRIVILEGES ON demo.* TO 'flow'@'%';
54+
GRANT ALL PRIVILEGES ON demo_upgrade.* TO 'flow'@'%';
55+
FLUSH PRIVILEGES;
56+
57+
database:
58+
dbName: "demo"
59+
dbUser: "flow"
60+
dbPassword: "flow_pass"
61+
dbType: "mariadb"
62+
dbPort: 3306
63+
clusterEndpoint: "mariadb"
64+
65+
##---------------------------------------------
66+
## Flow server admin credentials section
67+
##---------------------------------------------
68+
69+
flowCredentials:
70+
## Name of the secret containing the admin user password to use. If set, the admin user password
71+
## will be read from the secret instead of the plain-text `adminPassword` (not recommended for production).
72+
##
73+
## The data field must contain base64 encoded value for key 'CBF_SERVER_ADMIN_PASSWORD'.
74+
## E.g., kubectl create secret generic flow-admin-secret --from-literal=CBF_SERVER_ADMIN_PASSWORD='rrx!*d$z75Dsb'
75+
##
76+
## Uncomment the following line to set the name of the secret to use to read the admin user password.
77+
# existingSecret: flow-admin-secret
78+
##
79+
## IMPORTANT: This is clearly not meant for production use and is only meant for demo environments
80+
## where security may not be a concern. Use of `existingSecret` is preferred.
81+
adminPassword: changeme
82+

‎flow-on-kubernetes/cloudbees-flow-prod.yaml‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
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+
##---------------------------------------------
45+
## Flow storage configuration section
46+
##---------------------------------------------
47+
storage:
48+
volumes:
49+
serverPlugins:
50+
## A ReadWriteMany storage class used for plugins directory.
51+
## It is shared across all the Flow server and the web server
52+
## replicas.
53+
storageClass: your-readwritemany-storage-class
54+
55+
##---------------------------------------------
56+
## Flow server admin credentials section
57+
##---------------------------------------------
58+
59+
flowCredentials:
60+
## Name of the secret containing the admin user password to use.
61+
## The data field must contain base64 encoded value for key 'CBF_SERVER_ADMIN_PASSWORD'.
62+
## E.g., kubectl create secret generic your-flow-admin-secret --from-literal=CBF_SERVER_ADMIN_PASSWORD='rrx!*d$z75Dsb'
63+
##
64+
## Set the name of the secret that contains the admin user password.
65+
existingSecret: your-flow-admin-secret

0 commit comments

Comments
 (0)