Commit Graph

1483 Commits

Author SHA1 Message Date
Justin Santa Barbara 2b06a635cd Fix AWS storage manifest location 2017-01-05 01:34:41 -05:00
Kris Nova 67d6e90da4 Merge pull request #1304 from justinsb/storage_class
Create storage class on AWS
2017-01-04 21:10:43 -07:00
Justin Santa Barbara aa3128ef96 Update to kubedns 1.5 (including autoscaler)
Also harmonize the way we build addons
2016-12-30 11:18:17 -05:00
Justin Santa Barbara 4025c788d7 Create storage class on AWS 2016-12-29 00:20:50 -05:00
Chris Love 344e544615 Merge pull request #1290 from justinsb/hostnetwork_for_dns_controller
Run dnscontroller in host network, for faster bringup
2016-12-28 10:31:45 -07:00
Justin Santa Barbara 0f0089ece2 Reduce CPU request for kopeio vxlan 2016-12-28 11:41:05 -05:00
Justin Santa Barbara bd334cdceb Run dnscontroller in host network, for faster bringup 2016-12-28 11:18:05 -05:00
King'ori Maina 66f430c71e
Prefer Semantic Versioning
See:

* http://semver.org
* https://github.com/kubernetes/kops/issues/1081
2016-12-24 02:27:53 +02:00
King'ori Maina 267c0ca451
Upgrade Weave to 1.8.2
https://github.com/weaveworks/weave/releases/tag/v1.8.2
2016-12-23 21:48:16 +02:00
heschlie e18036cfa6 Renamed networking.calico
Renamed the networking.calico directory to networking.projectcalico.org
2016-12-22 16:23:08 -08:00
heschlie a4b7093b0d Calico integration
Adding the option to install Calico with the `--networking calico`
argument.  This will currently deploy Calico v2.0 to the cluster.

Documentation has also been updated with information about Calico and
where one can find more information or help.
2016-12-20 10:13:00 -08:00
Justin Santa Barbara fed68310fa Schema v1alpha2
* Zones are now subnets
* Utility subnet is no longer part of Zone
* Bastion InstanceGroup type added instead
* Etcd clusters defined in terms of InstanceGroups, not zones
* AdminAccess split into SSHAccess & APIAccess
* Dropped unused Multizone flag
2016-12-18 21:56:57 -05:00
chrislovecnm 1bbbe0b71d bumping weave version 2016-11-30 22:06:12 -07:00
chrislovecnm 6e9a88151a starting work on limits 2016-11-22 13:20:57 -07:00
chrislovecnm 25ee1e4cdb adding weave support 2016-11-16 15:48:32 -07:00
Justin Santa Barbara ee44353cde Add support for kopeio networking 2016-11-16 14:20:23 -05:00
Justin Santa Barbara a529ffbb65 Configure dns-controller with ID of hosted zones
Fix #584
2016-10-06 13:12:27 -04:00
Justin Santa Barbara 204d1364ac Switch to image published under kope account 2016-10-01 17:30:52 -04:00
Justin Santa Barbara 146babbd27 Disable ingress DNS integration for 1.4.0
There are still some problems with the default nginx controller
2016-10-01 17:25:11 -04:00
Justin Santa Barbara 1a4558a736 Fix DNS deployment manifest 2016-10-01 15:26:10 -04:00
Justin Santa Barbara 655a61588e Switch all the final switches for release 1.4
Also apply the 1.4 schema changes.
2016-10-01 13:50:19 -04:00
Justin Santa Barbara 3ead9fe0ce Create addons for 1.4
(It isn't activated yet though)
2016-10-01 09:35:20 -04:00
Justin Santa Barbara 6d139d06d1 Support labels on k8s nodes and AWS instances
A lot of supporting work was needed, including improvements to the model
and model generation logic.
2016-09-13 12:47:16 -04:00
Justin Santa Barbara 8fb4215e17 Run CI versions of k8s
CI versions are not pushed to gcr.io, so we need to preload the images
by downloading them and doing a docker load.
2016-08-11 01:32:42 -04:00
Justin Santa Barbara 2b3f55563e Run the master on the pod network, unless IsolateMaster=true
The master is now registered as a Node.  It is marked as Unschedulable,
so normal pods will not run on it.  But Daemonsets will, and it is
surprising that they don't work unless hostNetwork=true.

The default is now what seems to be expected:
* we allocate the master a real CIDR on the pod network
* kube-proxy runs on the master, so it can talk to pods
* we run kubelet on the master with enable-debugging-handlers, so
  kubectl logs etc works

To get the old behaviour, edit the cluster spec and set
`isolateMasters: true`
2016-07-28 12:12:16 -04:00
Justin Santa Barbara 5b8b4d4da3 Detect & delete new ASG launch configs
We now output a ClusterName property into the launchconfig, even though
we don't technically need it.  But it allows us to more easily detect
the cluster, and it generally seems like a good idea.

Also rename to 'autoscaling-config' and clean up the cluster name
detection logic.

Fix #96
2016-07-09 22:07:24 -04:00
Justin Santa Barbara ee325435e6 Rationalize properties to the minimal set 2016-06-26 09:45:05 -04:00
Justin Santa Barbara 93f634b428 upup: use vfs for secretstore/keystore
This is needed so that we can have encrypted storage and complex keys
(e.g. multiple CA certs).  Multiple CA certs are needed for an in-place
upgrade from kube-up v1.
2016-06-23 08:58:54 -04:00
Justin Santa Barbara 42e32f7379 upup: include kope-routing, but only if _kope_routing is set 2016-06-08 12:18:04 -04:00
Justin Santa Barbara 1eaf0d36a8 upup: HA support
Specifying multiple zones will bring up an HA cluster.
2016-06-07 15:44:00 -04:00
Justin Santa Barbara 71c2835007 upup: don't hard-code v1.2.2 in image names 2016-06-04 16:12:51 -04:00
Justin Santa Barbara a4408f76be upup: better secrets support
Start creating commands to manage secrets, and also stop implicitly
creating them.
2016-05-30 18:47:20 -04:00
Justin Santa Barbara caccb8953f UpUp: AWS support
Adds AWS support for both cloudup & nodeup.
Also cleaning up things found along the way!
2016-05-09 13:08:27 -04:00