* [stable/concourse] Tune fatal errors.
Remove guardian.api.garden-server.run.failed from the list of fatal errors,
this can be triggered merely from configuring a task to run a command that
doesn't exist.
* Update Chart.yaml
Make necessary improvements to Concourse worker lifecycle management.
Add additional fatal errors emitted as of Concourse 3.8.0 that should
trigger a restart, and remove "unkown volume" as one such error as this
will happen normally when running multiple concourse-web pods.
Try to start workers with a clean slate by cleaning up previous
incarnations of a worker. Call retire-worker before starting. Also
clear the concourse-work-dir before starting.
Call retire-worker in a loop and don't exit that loop until the old
worker is gone. This allows us to remove the fixed worker.postStopDelaySeconds
duration.
Add a note about persistent volumes being necessary.
Add containerPlacementStrategy, default random to better spread load
across workers.
In concourse, to expose prometheus metrics, need to set the env vars:
CONCOURSE_PROMETHEUS_BIND_IP = 0.0.0.0
CONCOURSE_PROMETHEUS_BIND_PORT = portnumber
This provides an HTTP endpoint to scrape the metrics.
Enabling metrics via the values.yaml is half the battle, still need to configure prometheus (potentially via service discovery and annotations) to scrape the data.
* provide configuration(s) for integrating Concourse with Vault
enabled configuring Concourse to use Vault for managing secrets, exposes 3 types of Auth Backends: tokens, approle, and TLS
* provide configuration(s) for integrating Concourse with Vault
enabled configuring Concourse to use Vault for managing secrets, exposes 3 types of Auth Backends: tokens, approle, and TLS
This can be helpful for users behind a corporate proxy who wish
to use resource types which require fetching containers images
from outside the organization's network.
* [stable/concourse] Add variable for the worker updateStrategy
This allows concourse users to change the update strategy for the
worker nodes. It defaults to using rolling updates.
* [stable/concourse] Bump Concourse version to 3.5.0
* [stable/concourse]web and worker assigned specified node with nodeAffinity
* [stable/concourse] web nodeport fixed if web.service.type is "NodePort"
* [stable/concourse] nodePort and nodeAffinity default value set
* [stable/concourse] modified README
* [stable/concourse] version increment
* take in https://github.com/kubernetes/charts/pull/2063#discussion_r143343633
* modified values.yaml
* modifed typo in web-svc.yaml
* web nodeAffinity parameter change to additionalAffinities (https://github.com/kubernetes/charts/pull/2300)
* add web.additionalAffinities comment to value.yaml
* modified README.md
* modified comment indent
* Make Concourse resilient to worker pod restarts.
Add time between worker stop and start. A shell is used to start the worker and sleep after the process terminates. SIGTERM is not propagated to the concourse process as a result, but this is actually desired for the shutdown process, below.
Gracefully de-register a worker using `retire-worker` instead of `land-worker` in the `preStop` hook. This tells concourse that the worker and its container volumes will not be coming back, which is the case when worker pods restart. Because SIGTERM doesn't reach the concourse process, `retire-worker` is the only mechanism used for graceful shutdown. If all containers are cleaned up within `worker.terminationGracePeriodSeconds`, the concourse process terminates on its own and the pod finishes terminating, otherwise the pod's container is killed. In either case, the worker disappears on ATC's end. See https://concourse.ci/worker-internals.html for more info.
Fixes https://github.com/kubernetes/charts/issues/2103
* Add a livenessProbe to Concourse workers that detects fatal errors.
Logs seem to be the only reliable way of detecting issues that prevent workers from taking on work. Tee the log to a file, and truncate it each time the livenessProbe runs.
Fixes https://github.com/kubernetes/charts/issues/2104
* Bump version to 0.7.0 and add myself to maintainers list.
* [stable/concourse] fix json to work with kubernetes v1.7
This updates @pfeodrippe's pull request to address
@unguiculus's comments. It moves the affinity into the
kubernetes 1.7 compatible affinity. It follows the pattern
used to fix cockroachdb in #1326.
Closes#1462, #1525, #1306
* [stable/concourse] Add worker statefulset annotations
This allows us to attach things like kube2iam annotations to
the stateful sets to allow Concourse workers to access private ECR
repositories.
* [stable/concourse] Bump chart version
* Support Concourse encryption key
* Bump chart version
* [stable/concourse] Bump version 0.3.2
* [stable/concourse] Add viglesiasce as maintainer
Also update frodenas to use GitHub ID
* Provide GitLab Auth configuration for main team
- Concourse 3.3.0 introduced GitLab OAuth provider
- These config changes will provide the ability to set GitLab auth configuration for the Concourse main team
- Update README.md and values.yml with placeholders
See related:
- http://concourse.ci/downloads.html#v330
- https://github.com/concourse/atc/pull/172
* [stable/concourse] Bump to 0.3.1
Default to naive for compatibility reasons, but a warning message will be shown on install or upgrade when naive is used.
Also set the default persistent volume size to 20Gi, 10Gi will easily run out of space.
Helps address kernel compatiblity issues with FS drivers, see https://github.com/concourse/concourse/issues/1230.
Fixes#1479.
* Conditional dependency on postgres.
Fixes#1056
* Update readme for conditional PostgreSQL dependency
Also add a section on restarting workers
* Update Chart.yaml