Spinnaker Create a Deployment Pipeline from UI: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 9: | Line 9: | ||
This article describes the mechanics of creating a deployment pipeline aimed at performing deployments into a Kubernetes cluster. Also see: {{Internal|Spinnaker_Concepts#Pipeline|Pipeline}} | This article describes the mechanics of creating a deployment pipeline aimed at performing deployments into a Kubernetes cluster. Also see: {{Internal|Spinnaker_Concepts#Pipeline|Pipeline}} | ||
= | =Pipeline Creation= | ||
Go to the Application to create the pipeline for, select "PIPELINES" from the left menu, and then click on the "Create" button at the top of the page. | Go to the Application to create the pipeline for, select "PIPELINES" from the left menu, and then click on the "Create" button at the top of the page. | ||
| Line 18: | Line 18: | ||
'''Copy From''': | '''Copy From''': | ||
=Pipeline Configuration= | |||
The pipeline configuration allows setting the following elements: | The pipeline configuration allows setting the following elements: | ||
==Execution Options== | |||
* [[Spinnaker_Concepts#Disable_concurrent_pipeline_executions_.28only_run_one_at_a_time.29|Disable concurrent pipeline executions (only run one at a time)]]. Set by default. | * [[Spinnaker_Concepts#Disable_concurrent_pipeline_executions_.28only_run_one_at_a_time.29|Disable concurrent pipeline executions (only run one at a time)]]. Set by default. | ||
* [[Spinnaker_Concepts#Do_not_automatically_cancel_pipelines_waiting_in_queue|Do not automatically cancel pipelines waiting in queue]] | * [[Spinnaker_Concepts#Do_not_automatically_cancel_pipelines_waiting_in_queue|Do not automatically cancel pipelines waiting in queue]] | ||
==Automated Triggers== | |||
All triggers require specifying permissions, which are the OD groups under whose identity the pipeline will operate when triggered. | All triggers require specifying permissions, which are the OD groups under whose identity the pipeline will operate when triggered. | ||
===Docker Registry Trigger=== | |||
For configuration, see: {{Internal|Spinnaker_Concepts#Docker_Registry|Docker Registry Trigger}} | For configuration, see: {{Internal|Spinnaker_Concepts#Docker_Registry|Docker Registry Trigger}} | ||
===Helm Chart Trigger=== | |||
For configuration, see: {{Internal|Spinnaker_Concepts#Helm_Chart_Trigger|Helm Chart Trigger}} | For configuration, see: {{Internal|Spinnaker_Concepts#Helm_Chart_Trigger|Helm Chart Trigger}} | ||
===Artifact Constraints=== | |||
The section specifies artifacts required for trigger to execute. Only one of the artifacts needs to be present for the trigger to execute. ⚠️ Note that only the artifacts specified here will execute the trigger, it is fine to leave empty if you need the trigger to be generated by arbitrary artifacts. | The section specifies artifacts required for trigger to execute. Only one of the artifacts needs to be present for the trigger to execute. ⚠️ Note that only the artifacts specified here will execute the trigger, it is fine to leave empty if you need the trigger to be generated by arbitrary artifacts. | ||
===Trigger Enabled=== | |||
Must be checked for the trigger to activate. | Must be checked for the trigger to activate. | ||
==Parameters== | |||
==Notifications== | |||
==Metadata== | |||
=Stages= | |||
==Render Helm== | |||
Renders a Helm manifest. | Renders a Helm manifest. | ||
{{Internal|Spinnaker_Stage_Bake_(Manifest)#Overview|Bake (Manifest)}} | {{Internal|Spinnaker_Stage_Bake_(Manifest)#Overview|Bake (Manifest)}} | ||
==Deploy Helm== | |||
Used to deploy Helm charts previously rendered by [[Spinnaker_Stage_Bake_(Manifest)#Overview|Bake (Manifest)]]. | Used to deploy Helm charts previously rendered by [[Spinnaker_Stage_Bake_(Manifest)#Overview|Bake (Manifest)]]. | ||
{{Internal|Spinnaker_Concepts#Deploy_.28Manifest.29|Deploy (Manifest)}} | {{Internal|Spinnaker_Concepts#Deploy_.28Manifest.29|Deploy (Manifest)}} | ||
==Manual Judgement== | |||
{{Internal|Spinnaker_Concepts#Manual_Judgement|Manual Judgement}} | {{Internal|Spinnaker_Concepts#Manual_Judgement|Manual Judgement}} | ||
=End State= | =End State= | ||
After a successful deployment, the application will be populated with the associated "cluster", "server group" and "load balancer". | After a successful deployment, the application will be populated with the associated "cluster", "server group" and "load balancer". | ||
Revision as of 00:30, 1 March 2022
External
- https://spinnaker.io/docs/guides/user/pipeline/managing-pipelines/#create-a-pipeline
- https://spinnaker.io/docs/guides/tutorials/codelabs/kubernetes-v2-source-to-prod/
Internal
Overview
This article describes the mechanics of creating a deployment pipeline aimed at performing deployments into a Kubernetes cluster. Also see:
Pipeline Creation
Go to the Application to create the pipeline for, select "PIPELINES" from the left menu, and then click on the "Create" button at the top of the page.
Type: Pipeline
Pipeline Name:
Copy From:
Pipeline Configuration
The pipeline configuration allows setting the following elements:
Execution Options
- Disable concurrent pipeline executions (only run one at a time). Set by default.
- Do not automatically cancel pipelines waiting in queue
Automated Triggers
All triggers require specifying permissions, which are the OD groups under whose identity the pipeline will operate when triggered.
Docker Registry Trigger
For configuration, see:
Helm Chart Trigger
For configuration, see:
Artifact Constraints
The section specifies artifacts required for trigger to execute. Only one of the artifacts needs to be present for the trigger to execute. ⚠️ Note that only the artifacts specified here will execute the trigger, it is fine to leave empty if you need the trigger to be generated by arbitrary artifacts.
Trigger Enabled
Must be checked for the trigger to activate.
Parameters
Notifications
Metadata
Stages
Render Helm
Renders a Helm manifest.
Deploy Helm
Used to deploy Helm charts previously rendered by Bake (Manifest).
Manual Judgement
End State
After a successful deployment, the application will be populated with the associated "cluster", "server group" and "load balancer".