Commit Graph

14 Commits

Author SHA1 Message Date
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
Shyam JVS
9305c37dec Revert "Add self anti-affinity to kube-dns pods" 2018-02-05 18:24:23 +01:00
Arto Jantunen
4565150f3d Add preferred self anti-affinity to kube-dns pods
This reverts commit 607c3d6967.
2018-01-24 10:12:34 +02:00
Rohit Ramkumar
ce40f8db7e Update kube-dns to 1.14.8 2018-01-05 15:00:40 -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
Bowei Du
c7d6934433 Update kube-dns 1.14.7
```release-notes
* Logging cleanups
* Updates kube-dns to use client-go 3
* Updates containers to use alpine as the base image on all platforms
* Adds support for IPv6
```
2017-10-23 14:37:13 -07:00
André Martins
3e4b9fad6a addons/dns: changing probes for SRV record type
Signed-off-by: André Martins <aanm90@gmail.com>
2017-10-20 20:07:25 +02:00
Shyam JVS
607c3d6967 Revert "kube-dns-anti-affinity: kube-dns never-co-located-in-the-same-node" 2017-10-18 22:01:42 +02:00
Kubernetes Submit Queue
ef87482923 Merge pull request #52193 from StevenACoffman/kube-dns-anti-affinity
Automatic merge from submit-queue (batch tested with PRs 53106, 52193, 51250, 52449, 53861). 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>.

kube-dns-anti-affinity: kube-dns never-co-located-in-the-same-node

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

This is upstreaming the kubernetes/kops#2705 pull request by @jamesbucher that was originally against [kops](github.com/kubernetes/kops).
Please see kubernetes/kops#2705 for more details, including a lengthy discussion.

Briefly, given the constraints of how the system works today:

+ if you need multiple DNS pods primarily for availability, then requiredDuringSchedulingIgnoredDuringExecution makes sense because putting more than one DNS pod on the same node isn't useful
+ if you need multiple DNS pods primarily for performance, then
preferredDuringScheduling IgnoredDuringExecution makes sense because it will allow the DNS pods to schedule even if they can't be spread across nodes

**Which issue this PR fixes**

fixes kubernetes/kops#2693

**Release note**:


```release-note
Improve resilience by annotating kube-dns addon with podAntiAffinity to prefer scheduling on different nodes.
```
2017-10-16 14:47:20 -07:00
Steve Coffman
e6540d422b kube-dns-anti-affinity: Adjust to match different scheme 2017-10-13 22:51:29 -04:00
Steve Coffman
786f460092 kube-dns-anti-affinity: kube-dns never-co-located-in-the-same-node 2017-10-12 14:22:32 -04:00
Christoph Blecker
e1d6bcc227 Add no-negcache flag to kube-dns 2017-10-09 11:20:57 -07:00
Zihong Zheng
db8f9ddcec Merge kube-dns templates into a single file 2017-10-03 09:43:52 -07:00