mirror of https://github.com/optim-enterprises-bv/kubernetes.git synced 2025-11-11 00:56:14 +00:00

Files

Kubernetes Submit Queue de0643106c Merge pull request #57756 from mborsz/exec-manifest

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Add 'exec' in all saltbase manifests using '/bin/sh -c'.

Right now, if docker sends SIGTERM, /bin/sh doesn't pass it to
underlying process, which breaks graceful process shutdown.

Changing '/bin/sh -c CMD > /var/log/FILE.log' pattern to '/bin/sh -c
exec CMD > /var/log/FILE.log' still allows to redirect output to log
file, but also passes all signals to CMD process.



**What this PR does / why we need it**:

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #57707, Fixes #45959

**Special notes for your reviewer**:

**Release note**:

```release-note
Fix to allow kubernetes components to react to SIGTERM signal and shutdown gracefully.
```

2018-01-03 02:25:42 -08:00

pillar

update oscodenames supporting systemd

2016-10-18 09:37:40 -04:00

reactor

Remove kube-up for vsphere

2016-12-22 20:15:37 +00:00

salt

Merge pull request #57756 from mborsz/exec-manifest

2018-01-03 02:25:42 -08:00

BUILD

Replace git_repository with http_archive and use ixdy's fork of bazel tools for pkg_tar

2017-05-03 10:13:06 -07:00

install.sh

Revert k8s.gcr.io vanity domain

2017-12-22 14:36:16 -08:00

README.md

Fix url for Saltstack administration document

2017-09-17 14:46:26 +08:00

README.md

SaltStack configuration

This is the root of the SaltStack configuration for Kubernetes. A high level overview for the Kubernetes SaltStack configuration can be found in the docs tree.

This SaltStack configuration currently applies to default configurations for Debian-on-GCE, Fedora-on-Vagrant, Ubuntu-on-AWS and Ubuntu-on-Azure. (That doesn't mean it can't be made to apply to an arbitrary configuration, but those are only the in-tree OS/IaaS combinations supported today.) As you peruse the configuration, these are shorthanded as gce, vagrant, aws, azure-legacy in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more: