-
Notifications
You must be signed in to change notification settings - Fork 71
SpinnakerConfig
Kevin Woo edited this page Oct 29, 2019
·
8 revisions
This is an example ConfigMap that is referenced by SpinnakerService.
Note that the metadata.name field in this example should match spec.spinnakerConfig.configMap.name on SpinnakerService manifest.
apiVersion: v1
kind: ConfigMap
metadata:
name: spinconfig-v001
data:
config: |
name: default
version: 1.15.2
...
profiles: |
gate:
default.apiPort: 8085
...
service-settings: |
gate:
artifactId: xxxxx
profiles__rosco__packer__aws-custom.json: |
{
"variables": {
"docker_source_image": "null",
"docker_target_image": null,
},
...
}
-
data.config
: the deployment configuration in the same format as in Halyard. For instance, given the following~/.hal/config
:currentDeployment: default deploymentConfigurations: - name: default version: 1.15.2 providers: ...
The
data.config
key would look like (de-nesting thedeploymentConfigurations
key):data: config: | name: default version: 1.15.2 providers: ...
-
data.profiles
: the content of the local profile files (~/.hal/<deployment>/profiles/
) by service name, e.g.:data: profiles: | gate: default.apiPort: 8085 ...
Profile data must be YAML parseable.
-
data.service-settings
: the content of the service settings file (~/.hal/<deployment>/service-settings/
) by service name, e.g.:data: service-settings: | gate: artifactId: xxxxx
Service settings data must be YAML parseable.
-
data.<relative path to other file>
: Other supporting files with a path relative to the main deployment. The file path is encoded with__
as a path separator. This includes other profile files such as a custom packer template inprofiles__rosco__packer__aws-custom.json
. These files are not parsed.