Commit Graph

15 Commits

Author SHA1 Message Date
Kenneth Owens
8fb609ba78 generated code 2017-08-09 15:19:47 -07:00
Kubernetes Submit Queue
3d91ba577d Merge pull request #50175 from foxish/update-strategies
Automatic merge from submit-queue

Change default update strategy to rolling update

Fixes https://github.com/kubernetes/kubernetes/issues/49604
Change default update strategy to rolling update for daemonset and statefulset in v1beta2

cc @kubernetes/sig-apps-pr-reviews @lukaszo @kargakis 

**Release note**:

```release-note
Make rolling update the default update strategy for v1beta2.DaemonSet and v1beta2.StatefulSet
```
2017-08-09 00:00:21 -07:00
Anirudh
37091c3744 Autogenerated 2017-08-08 15:24:12 -07:00
Janet Kuo
e245fbc2b2 Autogen 2017-08-07 19:11:39 -07:00
Janet Kuo
5473d56373 Remove some apps/v1beta2 generated files so that codegen works 2017-08-07 19:11:39 -07:00
Jun Xiang Tee
91f100b501 implement statefulset scale subresource 2017-08-07 12:17:46 -07:00
Kubernetes Submit Queue
8d6bbaa85f Merge pull request #49678 from smarterclayton/429_metric
Automatic merge from submit-queue

Timeout and Max-in-flight don't report non-resource URLs correctly.

Unify error reporting for 429 and 504 to be correct for timeout and max in flight and eviction. Add better messages to eviction (removing a todo). Return the correct body content for timeouts (reason and code should be correct).

This potentially increases cardinality of 429, but because non-api urls may be under the max-inflight budget we need to report them somewhere (if something breaks and starts fetching API versions endlessly).

```release-note
The 504 timeout error was returning a JSON error body that indicated it was a 500.  The body contents now correctly report a 500 error.
```
2017-08-05 01:28:00 -07:00
Di Xu
edaf66c276 auto-gen 2017-08-02 09:26:40 +08:00
Kubernetes Submit Queue
72c6251508 Merge pull request #47019 from jessfraz/allowPrivilegeEscalation
Automatic merge from submit-queue (batch tested with PRs 49651, 49707, 49662, 47019, 49747)

Add support for `no_new_privs` via AllowPrivilegeEscalation

**What this PR does / why we need it**:
Implements kubernetes/community#639
Fixes #38417

Adds `AllowPrivilegeEscalation` and `DefaultAllowPrivilegeEscalation` to `PodSecurityPolicy`.
Adds `AllowPrivilegeEscalation` to container `SecurityContext`.

Adds the proposed behavior to `kuberuntime`, `dockershim`, and `rkt`. Adds a bunch of unit tests to ensure the desired default behavior and that when `DefaultAllowPrivilegeEscalation` is explicitly set.

Tests pass locally with docker and rkt runtimes. There are also a few integration tests with a `setuid` binary for sanity.

**Release note**:

```release-note
Adds AllowPrivilegeEscalation to control whether a process can gain more privileges than it's parent process
```
2017-07-31 16:56:58 -07:00
Clayton Coleman
ddbc2ad9cf
generated: clarification on RetryAfterSeconds field 2017-07-31 18:39:34 -04:00
Janet Kuo
ac3f9b8c34 Autogen 2017-07-26 10:56:55 -07:00
Anirudh
c168a3faeb DS: autogen 2017-07-25 13:33:25 -07:00
mbohlool
75c474d4bc Update swagger and OpenAPI spec 2017-07-24 17:28:29 -07:00
Jess Frazelle
ed3b78635f
allowPrivilegeEscalation: update docs
Signed-off-by: Jess Frazelle <acidburn@google.com>
2017-07-24 13:55:13 -04:00
Janet Kuo
56f16346d2 Autogen
make clean && make generated_files && hack/update-all.sh
2017-07-20 14:16:43 -07:00