OpenShift BuildConfig Explained¶
Introduction¶
OpenShift builds turn source, binary input, or Dockerfile content into images. The useful troubleshooting path is BuildConfig, latest Build, build logs, output ImageStreamTag, and deployment trigger.
Before You Start¶
Make sure you are in the correct project and know whether the application is driven by a Deployment, DeploymentConfig, BuildConfig, ImageStream, or external registry image.
Practical Examples¶
oc get buildconfig web -n app
oc start-build web -n app --follow
oc logs build/web-1 -n app
oc get istag web:latest -n app
Example output:
NAME TYPE FROM LATEST
web Source Git@main 1
NAME TYPE FROM STATUS STARTED DURATION
web-1 Source Git@main Complete 2 minutes ago 1m10s
Example YAML¶
apiVersion: build.openshift.io/v1
kind: BuildConfig
metadata:
name: web
spec:
source:
git:
uri: https://github.com/example/web.git
strategy:
sourceStrategy:
from:
kind: ImageStreamTag
name: nodejs:18-ubi8
output:
to:
kind: ImageStreamTag
name: web:latest
Verification¶
oc describe buildconfig web -n app
oc logs build/web-1 -n app
oc get istag web:latest -n app
Troubleshooting¶
For build failures, inspect the build log first, then verify source access, builder image, output ImageStreamTag, and registry push permissions.
Common Mistakes¶
- Checking the Deployment before confirming the build produced an image.
- Using --follow and missing the final Build status.
- Forgetting that a BuildConfig trigger may start a new build automatically.
Quick Checklist¶
- Confirm the active project.
- Inspect the exact object named in the error.
- Read recent events.
- Apply one focused fix.
- Verify status after the change.
Related Guides¶
- Openshift New App Explained
- Openshift Imagestream Explained
- Openshift Application Deployment Checklist
Summary¶
OpenShift BuildConfig Explained should be verified with commands that match the OpenShift object being changed or investigated.