Skip to content

Commit

Permalink
add readme info about using secret for registry passwords
Browse files Browse the repository at this point in the history
  • Loading branch information
paulczar committed Jul 19, 2018
1 parent 668572f commit 40c50ac
Show file tree
Hide file tree
Showing 2 changed files with 26 additions and 1 deletion.
26 changes: 26 additions & 0 deletions stable/spinnaker/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,32 @@ for Spinnaker. If you want to add arbitrary clusters need to do the following:
deploymentContext: my-context
```

## Specifying Docker Registries and Valid Images (Repositories)

Spinnaker will only give you access to Docker images that have been whitelisted, if you're using a private registry or a private repository you also need to provide credentials. Update the following values of the chart to do so:
```yaml
dockerRegistries:
- name: dockerhub
address: index.docker.io
repositories:
- library/alpine
- library/ubuntu
- library/centos
- library/nginx
# - name: gcr
# address: https://gcr.io
# username: _json_key
# password: '<INSERT YOUR SERVICE ACCOUNT JSON HERE>'
# email: [email protected]
```
You can provide passwords as a Helm value, or you can use a pre-created secret containing your registry passwords. The secret should have an item per Registry in the format: `<registry name>: <password>`. In which case you'll specify the secret to use in `dockerRegistryAccountSecret` like so:

```yaml
dockerRegistryAccountSecret: myregistry-secrets
```

## Customizing your installation

### Manual
Expand Down
1 change: 0 additions & 1 deletion stable/spinnaker/templates/configmap/halyard-config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,6 @@ data:
{{ end }}
# Docker Registry
$HAL_COMMAND config provider docker-registry enable
{{- range $index, $registry := .Values.dockerRegistries }}
Expand Down

0 comments on commit 40c50ac

Please sign in to comment.