$ oc adm build-chain <image-stream>
- Documentation
- OKD
- Cluster Administration
- Building Dependency Trees
You are viewing documentation for a release that is no longer maintained. To view the documentation for the most recent version, see the latest OKD docs.
- About
- What's New?
- Getting Started
- Architecture
- Container Security Guide
- Installation and Configuration
- Overview
- Installing a Cluster
- Setting up the Registry
- Setting up a Router
- Upgrading a Cluster
- Master and Node Configuration
- Adding Hosts to an Existing Cluster
- Loading the Default Image Streams and Templates
- Configuring Custom Certificates
- Redeploying Certificates
- Configuring Authentication and User Agent
- Syncing Groups With LDAP
- Configuring LDAP failover
- Configuring the SDN
- Configuring Nuage SDN
- Configuring for AWS
- Configuring for OpenStack
- Configuring for GCE
- Configuring for Azure
- Configuring for VMWare vSphere
- Configuring Persistent Storage
- Overview
- Using NFS
- Using GlusterFS
- Using OpenStack Cinder
- Using Ceph RBD
- Using AWS Elastic Block Store
- Using GCE Persistent Disk
- Using iSCSI
- Using Fibre Channel
- Using Azure Disk
- Using Azure File
- Using FlexVolume
- Using VMware vSphere volumes for persistent storage
- Dynamic Provisioning and Creating Storage Classes
- Volume Security
- Selector-Label Volume Binding
- Enabling Controller-managed Attachment and Detachment
- Persistent Storage Examples
- Overview
- Sharing an NFS PV Across Two Pods
- Using Ceph RBD for persistent storage
- Using Ceph RBD for dynamic provisioning
- Complete Example Using GlusterFS
- Dynamic Provisioning Example Using Containerized GlusterFS
- Dynamic Provisioning Example Using Dedicated GlusterFS
- Containerized Heketi for Managing Dedicated GlusterFS
- Mounting Volumes To Privileged Pods
- Backing Docker Registry with GlusterFS Storage
- Binding Persistent Volumes by Label
- Using StorageClasses for Dynamic Provisioning
- Using StorageClasses for Existing Legacy Storage
- Configuring Azure Blob Storage for Integrated Docker Registry
- Working with HTTP Proxies
- Configuring Global Build Defaults and Overrides
- Configuring Pipeline Execution
- Configuring Route Timeouts
- Configuring Native Container Routing
- Routing from Edge Load Balancers
- Aggregating Container Logs
- Aggregate Logging Sizing Guidelines
- Enabling Cluster Metrics
- Customizing the Web Console
- Deploying External Persistent Volume Provisioners
- Cluster Administration
- Overview
- Managing Nodes
- Managing Users
- Managing Projects
- Managing Pods
- Managing Networking
- Configuring Service Accounts
- Managing Authorization Policies
- Image Policy
- Image Signatures
- Scoped Tokens
- Monitoring Images
- Managing Security Context Constraints
- Scheduling
- Setting Quotas
- Setting Multi-Project Quotas
- Setting Limit Ranges
- Pruning Objects
- Garbage Collection
- Allocating Node Resources
- Opaque Integer Resources
- Overcommitting
- Assigning Unique External IPs for Ingress Traffic
- Out of Resource Handling
- Monitoring and Debugging Routers
- High Availability
- IPtables
- Securing Builds by Strategy
- Restricting Application Capabilities Using Seccomp
- Sysctls
- Encrypting Data at Datastore Layer
- Encrypting Hosts with IPsec
- Building Dependency Trees
- Backup and Restore
- Troubleshooting Networking
- Diagnostics Tool
- Idling Applications
- Analyzing Cluster Capacity
- Scaling and Performance Guide
- CLI Reference
- Developer Guide
- Overview
- Application Life Cycle Management
- Authentication
- Authorization
- Projects
- Migrating Applications
- Tutorials
- Builds
- Deployments
- Templates
- Opening a Remote Shell to Containers
- Service Accounts
- Managing Images
- Quotas and Limit Ranges
- Injecting Information into Pods Using Pod Presets
- Getting Traffic into a Cluster
- Routes
- Integrating External Services
- Secrets
- ConfigMaps
- Downward API
- Projected Volumes
- Using Daemonsets
- Pod Autoscaling
- Managing Volumes
- Using Persistent Volumes
- Executing Remote Commands
- Copying Files
- Port Forwarding
- Shared Memory
- Application Health
- Events
- Managing Environment Variables
- Jobs
- Cron Jobs
- Create from URL
- Creating Images
- Using Images
- REST API Reference
×
Building Dependency Trees
Overview
OKD uses image
change triggers in a BuildConfig to detect when an
image
stream tag has been updated. You can use the oc adm build-chain command to
build a dependency tree that identifies which
images
would be affected by updating an image in a specified
image
stream.
The build-chain tool can determine which
builds
to trigger; it analyzes the output of those builds to determine if they will in
turn update another
image
stream tag. If they do, the tool continues to follow the dependency tree.
Lastly, it outputs a graph specifying the image stream tags
that would be impacted by an update to the top-level tag. The default output
syntax for this tool is set to a human-readable format; the DOT format is also
supported.
Usage
The following table describes common build-chain usage and general syntax:
| Description | Syntax |
|---|---|
Build the dependency tree for the latest tag in |
|
Build the dependency tree for the v2 tag in DOT format, and visualize it using the DOT utility. |
$ oc adm build-chain <image-stream>:v2 \
-o dot \
| dot -T svg -o deps.svg
|
Build the dependency tree across all projects for the specified image stream tag found the test project. |
$ oc adm build-chain <image-stream>:v1 \
-n test --all
|
|
You may need to install the graphviz package to use the |