Kubernetes · Arazzo Workflow
Kubernetes Deploy an Application into a New Namespace
Version 1.0.0
Create a namespace, seed its config and secrets, deploy the workload, and expose it behind a service.
View Spec
View on GitHub
AutomationCloud NativeCNCFContainersDeploymentOpen SourceOrchestrationScalingArazzoWorkflows
Provider
Workflows
deploy-application
Stand up a namespaced application with its config, secret, deployment, and service.
Provisions a namespace and then creates, in dependency order, the ConfigMap and Secret the workload consumes, the Deployment that runs it, and the Service that fronts it. Finishes by reading the Deployment status back.
1
createNamespace
createNamespace
Create the namespace that will scope every resource this workflow provisions, giving the application an isolated name and RBAC boundary.
2
createConfigMap
createNamespacedConfigMap
Write the application's non-confidential configuration into a ConfigMap so the pod template can consume it without baking values into the image.
3
createSecret
createNamespacedSecret
Store the application's credentials as an Opaque Secret using stringData, which the API server base64-encodes on write.
4
createDeployment
createNamespacedDeployment
Create the Deployment that runs the workload. The pod template selector matches the app label so the controller owns the pods it creates.
5
createService
createNamespacedService
Expose the deployment's pods behind a stable virtual IP and DNS name by selecting on the same app label the deployment applies to its pods.
6
verifyRollout
getNamespacedDeployment
Read the deployment back to confirm the controller observed the spec and report how many replicas are ready and available.