This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Concourse postgres conditional dependency #1390
Merged
viglesiasce
merged 3 commits into
helm:master
from
autonomic-ai:concourse-postgres-conditional-dependency
Jul 6, 2017
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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 |
---|---|---|
|
@@ -53,6 +53,30 @@ Scaling should typically be managed via the `helm upgrade` command, but `Statefu | |
$ kubectl scale statefulset my-release-worker --replicas=3 | ||
``` | ||
|
||
### Restarting workers | ||
|
||
If worker pods go down, their persistent volumes are changed, or if you're having other issues with them, you'll need to restart the workers. Concourse workers were designed to be deployed onto infrastructure VMs which are less "ephemeral" than pods, so it isn't good at detecting when a worker goes down and comes back under the same hostname. | ||
|
||
Scale the workers down to 0: | ||
|
||
``` | ||
kubectl scale statefulset concourse-worker --replicas=0 | ||
|
||
``` | ||
|
||
And then `fly workers` until the workers are detected to be `stalled`. Then for each worker | ||
``` | ||
fly prune-worker -w concourse-worker-0 | ||
fly prune-worker -w concourse-worker-1 | ||
... | ||
|
||
``` | ||
And finally | ||
|
||
``` | ||
kubectl scale statefulset concourse-worker --replicas=3 | ||
``` | ||
|
||
## Configuration | ||
|
||
The following tables lists the configurable parameters of the Concourse chart and their default values. | ||
|
@@ -110,6 +134,8 @@ The following tables lists the configurable parameters of the Concourse chart an | |
| `persistence.worker.class` | Concourse Worker Persistent Volume Storage Class | `generic` | | ||
| `persistence.worker.accessMode` | Concourse Worker Persistent Volume Access Mode | `ReadWriteOnce` | | ||
| `persistence.worker.size` | Concourse Worker Persistent Volume Storage Size | `10Gi` | | ||
| `postgresql.enabled` | Enable PostgreSQL as a chart dependency | `true` | | ||
| `postgresql.uri` | PostgreSQL connection URI | `nil` | | ||
| `postgresql.postgresUser` | PostgreSQL User to create | `concourse` | | ||
| `postgresql.postgresPassword` | PostgreSQL Password for the new user | `concourse` | | ||
| `postgresql.postgresDatabase` | PostgreSQL Database to create | `concourse` | | ||
|
@@ -244,3 +270,26 @@ web: | |
hosts: | ||
- concourse.domain.com | ||
``` | ||
|
||
|
||
### PostgreSQL | ||
|
||
By default, this chart will use a PostgreSQL database deployed as a chart dependency. You can also bring your own PostgreSQL. To do so, set the following in your custom `values.yaml` file: | ||
|
||
```yaml | ||
## Configuration values for the postgresql dependency. | ||
## ref: https://github.com/kubernetes/charts/blob/master/stable/postgresql/README.md | ||
## | ||
postgresql: | ||
|
||
## Use the PostgreSQL chart dependency. | ||
## Set to false if bringing your own PostgreSQL. | ||
## | ||
enabled: false | ||
|
||
## If bringing your own PostgreSQL, the full uri to use | ||
## e.g. postgres://concourse:[email protected]:5432/concourse?sslmode=require | ||
## | ||
uri: postgres://concourse:[email protected]:5432/concourse?sslmode=require | ||
|
||
``` |
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 |
---|---|---|
|
@@ -350,6 +350,17 @@ persistence: | |
## ref: https://github.com/kubernetes/charts/blob/master/stable/postgresql/README.md | ||
## | ||
postgresql: | ||
|
||
## Use the PostgreSQL chart dependency. | ||
## Set to false if bringing your own PostgreSQL. | ||
## | ||
enabled: true | ||
|
||
## If bringing your own PostgreSQL, the full uri to use | ||
## e.g. postgres://concourse:[email protected]:5432/concourse?sslmode=disable | ||
## | ||
# uri: | ||
|
||
### PostgreSQL User to create. | ||
## | ||
postgresUser: concourse | ||
|
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.
Would it be possible to specify a uri with credentials that are not known upfront? E.g. when existing postgres installation pulls password from a
secret
object in cluster