Kubernetes · Arazzo Workflow
Kubernetes Publish a ConfigMap and Roll Out Its Consumers
Version 1.0.0
Inventory existing ConfigMaps, publish the new configuration, then roll the deployment that reads it.
View Spec
View on GitHub
AutomationCloud-NativeCNCFContainersDeploymentOpen-SourceOrchestrationScalingArazzoWorkflows
Provider
Workflows
config-rollout
Publish a ConfigMap and force the consuming deployment to restart against it.
Inventories the namespace's ConfigMaps, creates the new one, reads the consuming deployment, and replaces it with a changed annotation so the rolling restart picks up the published configuration.
1
inventoryConfigMaps
List the namespace's ConfigMaps to record the configuration in place before this publish, giving the run an auditable before state.
2
publishConfigMap
Publish the ConfigMap holding the application's non-confidential configuration as UTF-8 key/value pairs.
3
readConsumer
Read the deployment that consumes the ConfigMap and capture its resourceVersion so the restart write is concurrency-safe.
4
rollConsumer
Replace the deployment with a changed pod-template annotation so the controller rolls the pods and they read the published configuration.
Source API Descriptions
openapi
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.