forked from helm/charts
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow user to specify registry credentials in values or via a premade secret. #18
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d681f66
support username/password for docker registry
paulczar 0e87bb6
fix variable condition for registrysecret
paulczar 668572f
remove rogue sleep command from debugging
paulczar 40c50ac
add readme info about using secret for registry passwords
paulczar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,6 +31,15 @@ dockerRegistries: | |
# password: '<INSERT YOUR SERVICE ACCOUNT JSON HERE>' | ||
# email: [email protected] | ||
|
||
# If you don't want to put your passwords into a values file | ||
# you can use a pre-created secret instead of putting passwords | ||
# (specify secret name in below `dockerRegistryAccountSecret`) | ||
# per account above with data in the format: | ||
# <name>: <password> | ||
|
||
# dockerRegistryAccountSecret: myregistry-secrets | ||
|
||
|
||
kubeConfig: | ||
# Use this when you want to register arbitrary clusters with Spinnaker | ||
# Upload your ~/kube/.config to a secret | ||
|
@@ -70,6 +79,10 @@ redis: | |
nodeSelector: {} | ||
cluster: | ||
enabled: false | ||
# Uncomment if you don't want to create a PVC for redis | ||
# master: | ||
# persistence: | ||
# enabled: false | ||
|
||
# Minio access/secret keys for the in-cluster S3 usage | ||
# Minio is not exposed publically | ||
|
@@ -81,6 +94,9 @@ minio: | |
secretKey: spinnakeradmin | ||
bucket: "spinnaker" | ||
nodeSelector: {} | ||
# Uncomment if you don't want to create a PVC for minio | ||
# persistence: | ||
# enabled: false | ||
|
||
gcs: | ||
enabled: false | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add something about this to the README as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done!