Commit Graph

15 Commits

Author SHA1 Message Date
ialidzhikov
20d44dfbfe Update Calico cpva to v0.8.2
Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>
2020-04-28 09:36:14 +03:00
ialidzhikov
0e93282a35 Clean up cluster-service label from calico-policy-controller
Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>
2019-11-14 17:32:57 +02:00
Kubernetes Prow Robot
5ced7377c3
Merge pull request #81428 from MrHohn/cpva-v0.8.1
Bump vertical autoscaler to v0.8.1
2019-08-23 17:58:50 -07:00
Zihong Zheng
dfe2e1a1ee Bump vertical autoscaler to v0.8.1 2019-08-14 11:26:31 -07:00
draveness
495faa22db feat: cleanup pod critical pod annotations feature 2019-08-09 08:41:23 +08:00
draveness
d83526d253 Revert "feat: cleanup pod critical pod annotations feature"
This reverts commit b6d41ee5cc.
2019-07-18 13:31:12 +08:00
draveness
b6d41ee5cc feat: cleanup pod critical pod annotations feature 2019-07-11 08:54:19 +08:00
Zihong Zheng
66086c32cf Bump cluster-proportional-vertical-autoscaler to 0.7.1 2019-05-13 13:22:27 -07:00
Jordan Liggitt
cc680273e8 Change add-on manifests to apps/v1 2018-12-19 17:30:59 -05:00
Kubernetes Submit Queue
7ef11bd964
Merge pull request #59237 from tanshanshan/addons1
Automatic merge from submit-queue (batch tested with PRs 59767, 56454, 59237, 59730, 55479). 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>.

Change critical pods’ template to use priority

**What this PR does / why we need it**:
Change critical pods’ template to use priority
Thanks.
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
ref #57471

**Special notes for your reviewer**:

**Release note**:

```release-note

```
2018-02-12 15:44:36 -08:00
tanshanshan
95b2b94b1b Change critical pods’ template to use priority 2018-02-08 15:06:27 +08:00
Tim Hockin
3586986416 Switch to k8s.gcr.io vanity domain
This is the 2nd attempt.  The previous was reverted while we figured out
the regional mirrors (oops).

New plan: k8s.gcr.io is a read-only facade that auto-detects your source
region (us, eu, or asia for now) and pulls from the closest.  To publish
an image, push k8s-staging.gcr.io and it will be synced to the regionals
automatically (similar to today).  For now the staging is an alias to
gcr.io/google_containers (the legacy URL).

When we move off of google-owned projects (working on it), then we just
do a one-time sync, and change the google-internal config, and nobody
outside should notice.

We can, in parallel, change the auto-sync into a manual sync - send a PR
to "promote" something from staging, and a bot activates it.  Nice and
visible, easy to keep track of.
2018-02-07 21:14:19 -08:00
Tim Hockin
e9dd8a68f6 Revert k8s.gcr.io vanity domain
This reverts commit eba5b6092a.

Fixes https://github.com/kubernetes/kubernetes/issues/57526
2017-12-22 14:36:16 -08:00
Tim Hockin
eba5b6092a Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
Gunjan Patel
05661b68eb Add RBAC, healthchecks, autoscaler and update Calico to v2.5.0, Typha to 0.4.0 2017-09-01 12:52:53 -07:00