Spinnaker Stage Deploy (Manifest): Difference between revisions
Line 14: | Line 14: | ||
====Override Namespace==== | ====Override Namespace==== | ||
⚠️ There were (yet not elucidated) situations when even if a specific [[Spinnaker_Stage_Bake_(Manifest)#Namespace|namespace configured in the Bake (Manifest) stage]] was ignored, and the deployment went to "default". That was fixed by overriding the namespace here. | ⚠️ There were (yet not elucidated) situations when even if a specific [[Spinnaker_Stage_Bake_(Manifest)#Namespace|namespace configured in the Bake (Manifest) stage]] was ignored, and the deployment went to "default". That was fixed by overriding the namespace here. | ||
===Namespace==== | ====Namespace==== | ||
===Manifest Configuration=== | ===Manifest Configuration=== | ||
====Manifest Source==== | ====Manifest Source==== |
Revision as of 01:05, 26 February 2022
External
- https://spinnaker.io/docs/guides/user/kubernetes-v2/deploy-helm/
- https://spinnaker.io/docs/guides/user/kubernetes-v2/traffic-management/
- https://spinnaker.io/docs/guides/user/kubernetes-v2/rollout-strategies/
Internal
Overview
Deploy a Kubernetes manifest yaml/json file. This section refers to deploying a Helm chart rendered by a previous Bake (Manifest) stage.
Configuration
Deploy (Manifest) Configuration
Basic Settings
Account
A Spinnaker account corresponds to a physical Kubernetes cluster. Must be previously configured.
Override Namespace
⚠️ There were (yet not elucidated) situations when even if a specific namespace configured in the Bake (Manifest) stage was ignored, and the deployment went to "default". That was fixed by overriding the namespace here.
Namespace
Manifest Configuration
Manifest Source
Artifact
Manifest Artifact
The display name of the manifest rendered at the Bake (Manifest) stage.
Expression Evaluation
Skip SpEL expression evaluation. Skip SpEL expression evaluation of the manifest artifact in this stage. Can be paired with the "Evaluate SpEL expressions in overrides at bake time" option in the Bake Manifest stage when baking a third-party manifest artifact with expressions not meant for Spinnaker to evaluate as SpEL.
Required Artifacts to Bind
These artifacts must be present in the context for this stage to successfully complete. Artifacts specified will be bound to the deployed manifest. TO PROCESS: https://spinnaker.io/docs/reference/artifacts-legacy/in-kubernetes-v2/#binding-artifacts-in-manifests.
Rollout Strategy Options
Enable
Allow Spinnaker to associate each ReplicaSet deployed in this stage with one or more Services and manage traffic based on your selected rollout strategy options.
Service(s) Namespace
Service(s)
Traffic
Send client requests to new pods
Strategy
The rollout strategy tells Spinnaker what to do with the previous version(s) of the ReplicaSet in the cluster.