Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 2. Build strategies
You can use a curated set of build strategies or cluster build strategies on the OpenShift Container Platform cluster. The Builds for Red Hat OpenShift Operator automatically installs these strategies for use. This automated installation of strategies helps you to quickly get started with Builds.
Builds supports the following cluster build strategies:
-
buildah: Supported on all platforms -
source-to-image: Supported on the linux/amd64 platform -
buildpacks: Supported on all platforms -
buildpacks-extender: Supported on all platforms
2.1. Buildah
The buildah cluster build strategy uses a Dockerfile to build a container image and pushes it to the target registry. You must specify the Dockerfile in the spec.paramValues field of the Build CR.
You can share the buildah strategy across different namespaces within your cluster because the Builds for Red Hat OpenShift Operator installs the buildah strategy at cluster level.
You can configure the following parameters for the buildah strategy:
| Name | Type | Description | Default |
|---|---|---|---|
|
| array | Key-value pair of the arguments required by the Dockerfile that is used during the build | [] |
|
| array | List of registries that must be blocked | [] |
|
| array | List of insecure registries with their fully qualified domain name (FQDN) | [] |
|
| array | List of registries to search short name images | ["registry.redhat.io", "quay.io"] |
|
| string | Path of the Dockerfile that is used during the build | "Dockerfile" |
|
| string |
Storage drivers that are used by | "vfs" |
|
| string | Sets the target stage to be built | "" |
For more information, see Configuring build strategies.
2.2. Source-to-image
This build strategy is composed of source-to-image and buildah. You can use this strategy to generate a container file and prepare the application to build with a builder image. You must specify the builder image in the spec.paramValues field of the Build CR.
You can share the source-to-image strategy across different namespaces within your cluster because the Builds for Red Hat OpenShift Operator installs the source-to-image strategy at cluster level.
You can configure the following parameters for the source-to-image strategy:
| Name | Type | Description | Default |
|---|---|---|---|
|
| array | List of registries that must be blocked | [] |
|
| array | List of insecure registries with their FQDN | [] |
|
| array | List of registries to search short name images | ["registry.redhat.io", "quay.io"] |
|
| string | Location of the builder image that is used during the build | NA |
|
| string |
Storage drivers that are used by | "vfs" |
2.3. Buildpacks
The buildpacks cluster build strategy uses Cloud Native Buildpacks (CNB) to build and push a container image from source code, without requiring a Dockerfile. The configuration details are provided through parameters in the Build resource.
The buildpacks-extender cluster build strategy supports the image extension feature of CNB, in addition to all the capabilities offered by the buildpacks strategy. The buildpacks-extender allows you to modify the builder or run image using a Dockerfile. This is useful for installing system dependencies or applying security configurations that standard Buildpacks cannot handle. The Dockerfile is provided by a Buildpack that supports extensions. To use the extender, set the cnb-extender-kind parameter in the Build resource.
The buildpacks cluster build strategy supports Quarkus and Go-based applications, while the buildpacks-extender cluster build strategy supports Node.js and Python-based applications.
You can configure the following parameters for the buildpacks strategy:
| Name | Type | Description | Default |
|---|---|---|---|
|
| string | Supported Platform API Version | "0.12" |
|
| string | Builder image containing the buildpacks | "" |
|
| string | Image to use while executing Lifecycle phases | "buildpacksio/lifecycle:0.20.8" |
|
| string | Logging levels | "debug"] |
|
| string | Reference to a run image to use | "" |
|
| string | Name of the persistent app cache image | "" |
|
| string | Subpath within the source input where the source to build is located | "" |
|
| array | Environment variables to set during build-time | [] |
|
| string | Name of the platform directory | "empty-dir" |
|
| string | User ID of the builder image user | "1001" |
|
| string | Group ID of the builder image user | "1001" |
|
| string | Absolute path to the user’s home directory | "/tekton/home" |
|
| string | Name of the Persistent Volume Claim for cache | "ws-pvc" |
|
| string |
The kind of image to extend ( | "" |
|
| string | Directory of extended layers, passed as -extended flag to the exporter | "/layers/extended" |
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}