Within the Kubernetes environment, Helm charts are the primary method to configure CloudBees CD/RO components. From configuring your license information and database connections to autoscaling and platform specific implementation, these charts provide a central location to configure most aspects of CloudBees CD/RO installations.
CloudBees CD/RO releases include default Helm charts that provide the values for a basic environment you can configure into a project-specific production environment. After doing so in a project-specific myvalues.yaml
, you can configure your CloudBees CD/RO Helm installation to use your values file with the helm install -f
option.
For more information, including helm
CLI commands for working with values files, refer to Helm values files.
You can integrate CloudBees CD/RO with various Kubernetes platform-specific providers. Some platform-specific integrations, such as OpenShift, have requirements and prerequisites that must be met to correctly install, operate, and upgrade CloudBees CD/RO. Some requirements must be made in CloudBees CD/RO server and agent values files, while others are made within the platform configuration prior to installing CloudBees CD/RO. For more information on platform-specific integrations, refer to Kubernetes platform-specific configurations. Additionally, CloudBees CD/RO documentation includes numerous how-tos for Kubernetes project-specific configurations. For help with CloudBees CD/RO on Kubernetes project-specific configurations, refer to Kubernetes configuration options. |
CloudBees CD/RO default Helm charts
CloudBees provides server and agent Helm charts with CloudBees CD/RO default values for both demo and production installations.
CloudBees strongly recommends that you create copies of your Helm charts and place them under version control as a project-specific myvalues.yaml . This makes tracking updates and changes between releases much easier.
|
Demo installations
For demo installations, refer to the GitHub cloudbees-example
public repository:
-
CloudBees CD/RO agent Helm chart.
For demo installations, not all configurations are possible. For instance, a built-in database is included to experiment with, but to configure your own database, you have must an enterprise license.
Production installations
A default values file (values.yaml
) is released for each CloudBees CD/RO version that contains all default values for the CloudBees CD/RO server installation as part of the cloudbees-flow
Helm chart. However, for production environments, there are many project-specific values that must be set in the cloudbees-flow
Helm chart according to your project’s implementation.
Your project-specific values, which are only a subset of the default values, are normally set in a separate myvalues.yaml
. This has the major advantage of reducing the amount of overall configuration you must track and maintain.
During installation, you can specify your project-specific myvalues.yaml
when running helm install
. Doing so, overwrites the default values in the values.yaml
with the project-specific values in your myvalues.yaml
, while still using the default values for items you did not customize.
CloudBees provides two ways to get started with your myvalues.yaml
:
-
You can start with the
values.yaml
and extract only the project-specific parts you need. To get started, refer to Use the default values file to create your project-specific values file. -
You can start with an example production values file and adapt it to fit your needs.To get started, refer to Use an example production values file to create your project-specific values file.
You can integrate CloudBees CD/RO with various Kubernetes platform-specific providers. Some platform-specific integrations, such as OpenShift, have requirements and prerequisites that must be met to correctly install, operate, and upgrade CloudBees CD/RO. Some requirements must be made in CloudBees CD/RO server and agent values files, while others are made within the platform configuration prior to installing CloudBees CD/RO. For more information on platform-specific integrations, refer to Kubernetes platform-specific configurations. Additionally, CloudBees CD/RO documentation includes numerous how-tos for Kubernetes project-specific configurations. For help with CloudBees CD/RO on Kubernetes project-specific configurations, refer to Kubernetes configuration options. |
Use the default values file to create your project-specific values file
To get started using the values.yaml
to create your myvalues.yaml
chart:
-
Add the CloudBees Helm chart repository to your local Helm client by running:
helm repo add cloudbees https://charts.cloudbees.com/public/cloudbees helm repo update
-
Create a local copy of the latest
cloudbees-flow
value file (v2025.03.0.178767
) by running:helm show values cloudbees/cloudbees-flow > myvalues.yaml
-
Go through your
myvalues.yaml
and update it to meet your project-specific needs. Specifically, configure your database, storage, license information, and CloudBees CD/RO credentials before installing it. For information on available configuration options, refer to:By default, CloudBees CD/RO uses a built-in database for development and testing. For production, you must configure CloudBees CD/RO to connect to your project-specific database. Refer to Supported platforms for CloudBees CD/RO on Kubernetes for supported databases.
A CloudBees CD/RO enterprise license is required to use a project-specific database. To prevent installation errors, configure both the license and database connection in your
myvalues.yaml
before installing thecloudbees-flow
chart. Missing either can trigger configuration or licensing errors.To install CloudBees CD/RO with an existing database, refer to How to install CloudBees CD/RO on Kubernetes using an existing database.
You can switch from the built-in to an external database later. For details, refer to Configure CloudBees CD/RO to use an alternate database.
If the database connection fails, ensure the license is valid and the configuration is correct. For more information, refer to Configure an external database.
-
In v2024.06.0 or later values files, the
dois
andanalytics
workloads are both enabled by default. However, only theanalytics
workload is required by new installations.To avoid unneeded resource consumption caused by the
dois
workload, refer to Disable legacy CloudBees Analytics in Helm charts before installing CloudBees CD/RO. -
(Optional) If you are using a multi-node deployment for the CloudBees Analytics server, a common node certificate infrastructure is required. Refer to Configure CloudBees Analytics server certificates to learn how to configure common node certificate infrastructure in your project-specific values file.
-
(Optional) Place your
myvalues.yaml
under version control. CloudBees strongly suggests you do this to track updates and compare changes between releases. -
(Optional) Any configurations not specified in your
myvalues.yaml
are automatically taken from thevalues.yaml
during installation. This means, you can also delete any configuration options in yourmyvalues.yaml
that are not specifically required by your project. This helps to reduce the overall configurations maintained in this file.While deleting unneeded configuration options, ensure you maintain valid tag nesting and syntax. Failing to do so may cause your installation to fail or produce unpredictable behavior on your platform.
After you have configured your myvalues.yaml
, refer to Install CloudBees CD/RO production server.
Use an example production values file to create your project-specific values file
Preconfigured production Helm chart examples are available in the CloudBees examples repository to get you started. These files include:
Values file | Description |
---|---|
|
File for use with production installations. You must configure your database, storage, and CloudBees CD/RO credentials in a local project-specific values file before it can be used. For information on available configuration options, refer to cloudbees-flow chart configuration values. |
|
File listing all Helm chart values along and their default value. Use as a reference when specifying additional configurations in your local project-specific values file. For information on available configuration options, refer to cloudbees-flow chart configuration values. |
There are several platform versions of the production example Helm charts available in the CloudBees examples repository, each with prod in the YAML file name.
|
To create your myvalues.yaml
based on the example production chart:
-
Go to the CloudBees examples repository and save a copy of the example production chart you want to use as your project-specific
myvalues
.yaml. -
Go through your
myvalues.yaml
and update it to meet your project-specific needs. Specifically, configure your database, storage, license information, and CloudBees CD/RO credentials before installing it. For information on available configuration options, refer to cloudbees-flow chart configuration values.By default, CloudBees CD/RO uses a built-in database for development and testing. For production, you must configure CloudBees CD/RO to connect to your project-specific database. Refer to Supported platforms for CloudBees CD/RO on Kubernetes for supported databases.
A CloudBees CD/RO enterprise license is required to use a project-specific database. To prevent installation errors, configure both the license and database connection in your
myvalues.yaml
before installing thecloudbees-flow
chart. Missing either can trigger configuration or licensing errors.To install CloudBees CD/RO with an existing database, refer to How to install CloudBees CD/RO on Kubernetes using an existing database.
You can switch from the built-in to an external database later. For details, refer to Configure CloudBees CD/RO to use an alternate database.
If the database connection fails, ensure the license is valid and the configuration is correct. For more information, refer to Configure an external database.
-
In v2024.06.0 or later values files, the
dois
andanalytics
workloads are both enabled by default. However, only theanalytics
workload is required by new installations.To avoid unneeded resource consumption caused by the
dois
workload, refer to Disable legacy CloudBees Analytics in Helm charts before installing CloudBees CD/RO. -
(Optional) If you are using a multi-node deployment for the CloudBees Analytics server, a common node certificate infrastructure is required. Refer to Configure CloudBees Analytics server certificates to learn how to configure common node certificate infrastructure in your project-specific values file.
-
(Optional) Place your
myvalues.yaml
under version control. CloudBees strongly suggests you do this to track updates and compare changes between releases.
After you have configured your myvalues.yaml
, refer to Install CloudBees CD/RO production server.
cloudbees-flow chart configuration values
The following sections provide commands to retrieve the default values for the latest CloudBees CD/RO cloudbees-flow
Helm charts and version-specific charts.
If you have not already done so, add the CloudBees Helm chart repository to your local Helm client:
|
For each chart, there are multiple command options:
-
Display: Prints the
2025.03.0.178767
(latest) default values in your terminal. -
Copy to file (CTF): Copies the default chart values for
2025.03.0.178767
(latest) to a file in your current directory, named after the specific Helm chart (example:flow-global-values.yaml
).The file name does not include the version in the file name. If there is an existing version of the file in the directory, it will be overwritten. If you want to create files that contain the version in the file name, such as for archiving, use the Version-specific CTF command. -
Version-specific CTF: Copies version-specific default chart values to a file in your current directory, named after the specified version and specific Helm chart (example:
flow-global-2025.03.0.178767-values.yaml
).For the Version-specific CTF commands listed below, you must enter the CloudBees CD/RO APP VERSION for your release. You can retrieve the APP VERSION for your release by running:
helm search repo cloudbees/cloudbees-flow --versions | grep '^cloudbees/cloudbees-flow[[:space:]]'
Global values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Global configurations section.
Global configurations
helm show values cloudbees/cloudbees-flow | awk ' /^### Global configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Global configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-global-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Global configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-global-$APP_VERSION-values.yaml
Images values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Common images configurations section.
Common images configurations
helm show values cloudbees/cloudbees-flow | awk ' /^### Common images configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Common images configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-common-images-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Common images configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-common-images-$APP_VERSION-values.yaml
Ingress values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Ingress configuration section.
Ingress configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Ingress configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Ingress configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-ingress-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Ingress configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-ingress-$APP_VERSION-values.yaml
CloudBees CD/RO server values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow server configuration section.
Flow server configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-$APP_VERSION-values.yaml
CloudBees CD/RO web server values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow web server configuration section.
Flow web server configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow web server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow web server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-web-server-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow web server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-web-server-$APP_VERSION-values.yaml
Repository values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow repository configuration section.
Flow repository configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow repository configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow repository configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-repository-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow repository configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-repository-$APP_VERSION-values.yaml
CloudBees Analytics server values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Analytics server configuration section.
In v2024.06.0 or later values files, the To avoid unnecessary resource consumption caused by the |
Analytics server configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Analytics server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Analytics server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-analytics-server-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Analytics server configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-analytics-server-$APP_VERSION-values.yaml
Bound agent values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow bound agent configuration section.
If you are using a flowCredentials.existingSecret , you must configure the same existingSecret for the bound agent. For more information, refer to Kubernetes configuration options.
|
Flow bound agent configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow bound agent configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow bound agent configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-bound-agent-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow bound agent configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-bound-agent-$APP_VERSION-values.yaml
Server storage values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow storage configuration section.
Flow storage configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow storage configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow storage configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-storage-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow storage configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-storage-$APP_VERSION-values.yaml
Database values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow server database configuration section.
Flow server database configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server database configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server database configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-database-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow server database configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-database-$APP_VERSION-values.yaml
CloudBees CD/RO credential values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow server credentials configuration section.
Flow server credentials configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server credentials configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server credentials configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-credentials-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow server credentials configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-credentials-$APP_VERSION-values.yaml
CloudBees CD/RO server license values (optional)
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow server license configuration section.
Flow server license configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server license configuration optional section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow server license configuration optional section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-license-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow server license configuration optional section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-server-license-$APP_VERSION-values.yaml
Pods security context values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Pods security context section.
Pods security context
helm show values cloudbees/cloudbees-flow | awk ' /^### Pods security context/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Pods security context/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-pods-security-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Pods security context/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-pods-security-$APP_VERSION-values.yaml
RBAC resources values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the RBAC resources section.
RBAC resources
helm show values cloudbees/cloudbees-flow | awk ' /^### RBAC resources/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### RBAC resources/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-rbac-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### RBAC resources/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-rbac-$APP_VERSION-values.yaml
Network isolation values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Network isolation configuration section.
Network isolation configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Network isolation configuration/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Network isolation configuration/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-network-isolation-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Network isolation configuration/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-network-isolation-$APP_VERSION-values.yaml
Zookeeper values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Zookeeper configuration section.
Zookeeper configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Zookeeper configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Zookeeper configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-zookeeper-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Zookeeper configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-zookeeper-$APP_VERSION-values.yaml
CloudBees CD/RO flow ingress values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Flow ingress configuration section.
CloudBees CD/RO’s
Per Kubernetes ingress specification, this is not supported. However, this is available as a non-standard extension of nginx-ingress, which is why ingress is bundled with CloudBees CD/RO. |
Ingress-nginx values
For CloudBees CD/RO v2025.03.0 or earlier, the default CloudBees CD/RO Helm chart includes a dependent ingress-nginx controller version affected by several known vulnerabilities, which could lead to critical security issues. These vulnerabilities affect ingress-nginx versions To mitigate these issues, update the ingress-nginx controller image tag to a secure version (starting with
|
Flow ingress configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow ingress configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Flow ingress configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-ingress-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Flow ingress configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-ingress-$APP_VERSION-values.yaml
CloudBees CD/RO miscellaneous values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow
values referenced in the values.yaml
under the Miscellaneous configuration section.
Miscellaneous configuration
helm show values cloudbees/cloudbees-flow | awk ' /^### Miscellaneous configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow | awk ' /^### Miscellaneous configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-miscellaneous-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow --version "$CHART_VERSION" | awk ' /^### Miscellaneous configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-miscellaneous-$APP_VERSION-values.yaml
cloudbees-flow-agent chart configuration values
The following sections provide commands to retrieve the default values for the latest CloudBees CD/RO cloudbees-flow-agent
Helm charts and version-specific charts.
For each chart, there are multiple command options:
-
Display: Prints the
2025.03.0.178767
default values in your terminal. -
Copy to file (CTF): Copies the default chart values for
2025.03.0.178767
to a file in your current directory, named after the specific Helm chart (example:flow-global-values.yaml
).The file name does not include the version in the file name. If there is an existing version of the file in the directory, it will be overwritten. If you want to create files that contain the version in the file name, such as for archiving, use the Version-specific CTF command. -
Version-specific CTF: Copies version-specific default chart values to a file in your current directory, named after the specified version and specific Helm chart (example:
flow-global-2025.03.0.178767-values.yaml
)..For the Version-specific CTF commands listed below, you must enter the CloudBees CD/RO agent APP VERSION for your release. You can retrieve the APP VERSION for your agent installation by running:
helm search repo cloudbees/cloudbees-flow-agent --versions
CloudBees CD/RO agent image values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow-agent
values referenced in the agent values.yaml
under the Common images configurations section.
Flow agent common images configurations
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Common images configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Common images configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-common-images-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow-agent --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Common images configurations section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-common-images-$APP_VERSION-values.yaml
CloudBees CD/RO agent configuration values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow-agent
values referenced in the agent values.yaml
in the Flow agent configuration section.
Flow agent configuration
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Flow agent configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Flow agent configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow-agent --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Flow agent configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-$APP_VERSION-values.yaml
CloudBees CD/RO agent pod scheduling values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow-agent
values referenced in the agent values.yaml
in the Pod scheduling settings section.
Flow agent pod scheduling settings
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Pod scheduling settings/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Pod scheduling settings/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-pod-scheduling-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow-agent --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Pod scheduling settings/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-pod-scheduling-$APP_VERSION-values.yaml
CloudBees CD/RO agent storage and resources values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow-agent
values referenced in the agent values.yaml
in the Flow agent storage and resources configuration section.
Flow agent storage and resources configuration
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Flow agent storage and resources configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Flow agent storage and resources configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-storage-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow-agent --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Flow agent storage and resources configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-storage-$APP_VERSION-values.yaml
CloudBees CD/RO agent credential values
CloudBees CD/RO server credentials are used to register your agent as a resource on the CloudBees CD/RO server. The admin
user is used by default. However, you may use a different user if desired. The user must have modify
permissions on CloudBees CD/RO server resources
.
You can find these cloudbees-flow-agent
values referenced in the agent values.yaml
.of the under the Flow server credentials configuration section.
Flow agent credentials
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Flow server credentials configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Flow server credentials configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-credentials-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow-agent --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Flow server credentials configuration section/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-credentials-$APP_VERSION-values.yaml
CloudBees CD/RO agent pod security context values
For the default CloudBees CD/RO Helm charts, refer to CloudBees CD/RO default Helm charts. You can find these cloudbees-flow-agent
values referenced in the agent values.yaml
in the Pods security context section.
Flow agent pod security context
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Pods security context/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } '
helm show values cloudbees/cloudbees-flow-agent | awk ' /^### Pods security context/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-pod-security-values.yaml
APP_VERSION="2025.03.0.178767" CHART_VERSION=$(helm search repo cloudbees/cloudbees-flow-agent --versions | awk -v app="$BUILD_VERSION" '$3 == app {print $2; exit}') helm show values cloudbees/cloudbees-flow-agent --version "$CHART_VERSION" | awk ' /^### Pods security context/ {f=1; print; next} f && /^### -+/ && ++dash_seen == 2 { exit } f { print } ' > flow-agent-pod-security-$APP_VERSION-values.yaml